Homepage

@semantic-release/error vulnerabilities

errors with more than just a message
Licenses: MIT
Published: 10 years ago Last updated: 2 years ago Latest version: 4.0.0 Latest non-vulnerable version: 4.0.0
npm
GitHub

Package Health Score

76/100
  • securityNo known security issues
  • popularityInfluential project
  • maintenanceSustainable
  • communityLimited

Maintenance

SUSTAINABLE

Commit Frequency

Loading chart...

Open Issues
2
Open PR
2
New PRS
1
Last Release
2 years ago
Last Commit
3 days ago
Maintainers
4

Further analysis of the maintenance status of @semantic-release/error based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for @semantic-release/error 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

INFLUENTIAL PROJECT
Weekly downloads (4.4M)
GitHub Stars
11
Forks
7
Contributors
20

The npm package @semantic-release/error receives a total of 4,412,399 downloads a week. As such, we scored @semantic-release/error popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @semantic-release/error, we found that it has been starred 11 times.

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

Community

LIMITED
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No
LICENSE
MIT

With more than 10 contributors for the @semantic-release/error 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 @semantic-release/error 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

NO KNOWN SECURITY ISSUES
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

No vulnerabilities found

Package versions

8 VERSIONS IN TOTAL
versionpublisheddirect vulnerabilities
4.0.07 Jun, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.017 Sep, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.0-beta.13 Sep, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.2.010 Feb, 2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.1.029 Oct, 2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.129 Oct, 2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.0.025 Sep, 2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.014 Jul, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

@semantic-release/error development dependencies

4 IN TOTAL
avac8codecovprettier