@nodesecure/scanner

v5.3.0

A package API to run a static analysis of your module's dependencies. For more information about how to use this package see README

Latest version published 4 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

69 / 100

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
5.3.0 | 01/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.2.1 | 12/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.0 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.8.2 | 01/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.7.0 | 06/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (79)

Download trend
GitHub Stars
27
Forks
14
Contributors
20

Direct Usage Popularity

Occasionally

The npm package @nodesecure/scanner receives a total of 79 downloads a week. As such, we scored @nodesecure/scanner popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @nodesecure/scanner, we found that it has been starred 27 times.

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

Community

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

With more than 10 contributors for the @nodesecure/scanner 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 @nodesecure/scanner is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 69/100 package health 69/100

Maintenance

Healthy

Commit Frequency

Open Issues
5
Open PR
5
Last Release
4 months ago
Last Commit
1 month ago

Further analysis of the maintenance status of @nodesecure/scanner based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @nodesecure/scanner demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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.

Package

Node.js Compatibility
>=18

Age
3 years
Dependencies
17 Direct
Versions
33
Install Size
73 kB
Dist-tags
2
# of Files
34
Maintainers
5
TS Typings
No

@nodesecure/scanner 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.