security-context

v4.0.0

Security Context

Unrecognized
Latest version published 2 years ago
    npm install security-context
  
We couldn't find any similar packages Browse all packages

Package Health Score

64 / 100

Popularity

Small

Weekly Downloads (3,232)

Download trend
Dependents
10
GitHub Stars
11
Forks
12
Contributors
20

Direct Usage Popularity

Uncommon

The npm package security-context receives a total of 3,232 downloads a week. As such, we scored security-context popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package security-context, we found that it has been starred 11 times, and that 10 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

01/2019
03/2019
05/2019
07/2019

Direct Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
4.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
4.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1
  • 0
    H
  • 0
    M
  • 0
    L
Popular
4.0.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Unrecognized

Security Policy
No

We found a way for you to contribute to the project! Looks like security-context 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 security-context
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
45
Open PR
3
Last Release
2 years ago
Last Commit
27 days ago

Further analysis of the maintenance status of security-context 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 security-context 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the security-context repository, this is possibly a sign for a growing and inviting community.

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


Embed Package Health Score Badge

package health: 64/100 package health 64/100

Package

Node.js Compatibility
not defined

Age
3 years
Dependencies
0 Direct
Versions
6
Install Size
15 kB
Dist-tags
1
# of Files
9
Maintainers
4
TS Typings
No

security-context 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.