Homepage

@nodesecure/vuln vulnerabilities

NodeSecure vulnerabilities strategies
Licenses: MIT
Published: 4 years ago Last updated: 3 years ago Latest version: 1.7.0 Latest non-vulnerable version: 1.7.0
npm
GitHub

Package Health Score

45/100
  • securitySecurity review needed
  • popularityLimited
  • maintenanceInactive
  • communitySustainable

Maintenance

INACTIVE
DEPRECATED

Commit Frequency

Loading chart...

Open Issues
5
Open PR
3
New PRS
1
Last Release
3 years ago
Last Commit
10 days ago
Maintainers
6

Further analysis of the maintenance status of @nodesecure/vuln 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 @nodesecure/vuln 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.

Popularity

LIMITED
Weekly downloads (263)
GitHub Stars
30
Forks
13
Contributors
20

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

Based on project statistics from the GitHub repository for the npm package @nodesecure/vuln, we found that it has been starred 30 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
LICENSE
MIT

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

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

SECURITY REVIEW NEEDED
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

No vulnerabilities found

Package versions

11 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
1.7.030 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.6.05 Mar, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.5.022 Jan, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.4.128 Nov, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.4.031 Oct, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.3.010 Sep, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.012 Aug, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.011 Aug, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.211 Aug, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.111 Aug, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

@nodesecure/vuln dependencies

5 IN TOTAL
semver@slimio/github@npmcli/arborist@myunisoft/httpie@nodesecure/npm-registry-sdk

@nodesecure/vuln development dependencies

8 IN TOTAL
c8tsdtapecross-env@slimio/is@small-tech/tap-monkey@nodesecure/eslint-config@small-tech/esm-tape-runner