Homepage

should-semantic-release vulnerabilities

Checks whether a semantic release should be run for a repository. 💂
Licenses: MIT
Published: 2 years ago Last updated: 26 days ago Latest version: 0.3.5 Latest non-vulnerable version: 0.3.5
npm
GitHub

Package Health Score

78/100
  • securityNo known security issues
  • popularitySmall
  • maintenanceHealthy
  • communitySustainable

Maintenance

HEALTHY

Commit Frequency

Loading chart...

Open Issues
1
Open PR
6
New PRS
1
Last Release
26 days ago
Last Commit
3 days ago
Maintainers
1

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

We found that should-semantic-release demonstrates a positive version release cadence with at least one new version released in the past 3 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.

Popularity

SMALL
Weekly downloads (3.6k)
GitHub Stars
13
Forks
4
Contributors
0

The npm package should-semantic-release receives a total of 3,623 downloads a week. As such, we scored should-semantic-release popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package should-semantic-release, we found that it has been starred 13 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
Yes
Contributors
0
Funding
Yes
LICENSE
MIT

This project has seen only 10 or less contributors.

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

14 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
0.3.511 Nov, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.425 Jun, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.33 Apr, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.23 Apr, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.116 Feb, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.018 Feb, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.2.12 Oct, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.2.02 Oct, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.1.14 Apr, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.1.04 Apr, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

should-semantic-release dependencies

2 IN TOTAL
@pkgjs/parseargsconventional-commits-parser

should-semantic-release development dependencies

35 IN TOTAL
@eslint-community/eslint-plugin-eslint-comments@eslint/js@release-it/conventional-changelog@types/eslint-plugin-markdown@types/node@types/pkgjs__parseargs@vitest/coverage-v8@vitest/eslint-pluginconsole-fail-testcreate-typescript-appcspelleslinteslint-plugin-jsdoceslint-plugin-jsonceslint-plugin-markdowneslint-plugin-neslint-plugin-package-jsoneslint-plugin-perfectionisteslint-plugin-regexpeslint-plugin-yml
Show more dependencies