safe-access

v0.1.0

A utility to allow for safe accessing of nested properties

MIT
Latest version published 8 years ago
    npm install safe-access
  

Package Health Score

45 / 100

Popularity

Small

Weekly Downloads (6,318)

Download trend
Dependents
21
GitHub Stars
47
Forks
5
Contributors
2

Direct Usage Popularity

TOP 10%

The npm package safe-access receives a total of 6,318 downloads a week. As such, we scored safe-access popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package safe-access, we found that it has been starred 47 times, and that 21 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

03/2014

Direct Vulnerabilities

Popular
0.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.1.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like safe-access is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test safe-access
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
2
Open PR
1
Last Release
8 years ago
Last Commit
7 years ago

Further analysis of the maintenance status of safe-access based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for safe-access is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
2
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like safe-access is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
0 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

safe-access has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.