conventional-recommended-bump
Get a recommended version bump based on conventional commits.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/bumper.js | AI (source-diff): dist/ contains compiled TypeScript output with long lines from bundling, not obfuscation. Code is fully readable. Standard for this monorepo's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/cli/index.js | AI (source-diff): dist/cli/ is compiled TypeScript CLI output. Samples show plain readable JS with CLI help text and flag definitions. Not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cli/options.js | AI (source-diff): dist/cli/options.js is compiled TypeScript output. Samples show plain readable option-parsing functions. Not obfuscated. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects migration to a more complete dist bundle absorbing git-client functionality. Consistent with the dep swap from git-raw-commits/git-semver-tags to @conventional-changelog/git-client. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @conventional-changelog/git-client is a first-party package from the same conventional-changelog monorepo org, replacing git-raw-commits and git-semver-tags. Legitimate internal refactor. | ai | |
| phantom-deps | phantom-dep:conventional-commits-filter | AI (phantom-deps): conventional-commits-filter is explicitly listed as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 11.2.0 | 5 / 0 | |
| 11.1.0 | 5 / 0 | |
| 11.0.0 | 5 / 0 | |
| 10.0.0 | 5 / 0 | |
| 9.0.0 | 6 / 1 | |
| 8.0.0 | 7 / 1 | |
| 7.0.1 | 7 / 1 | |
| 7.0.0 | 7 / 1 | |
| 6.1.0 | 8 / 1 | |
| 6.0.12 | 8 / 1 | |
| 6.0.11 | 8 / 0 | |
| 6.0.10 | 8 / 0 | |
| 6.0.9 | 8 / 0 | |
| 6.0.5 | 8 / 0 | |
| 6.0.4 | 8 / 0 | |
| 6.0.3 | 8 / 0 | |
| 6.0.2 | 8 / 0 | |
| 6.0.0 | 8 / 0 | |
| 5.0.1 | 8 / 0 | |
| 5.0.0 | 8 / 0 | |
| 4.1.1 | 8 / 0 | |
| 4.0.4 | 8 / 0 | |
| 4.0.3 | 8 / 0 | |
| 4.0.1 | 8 / 4 | |
| 4.0.0 | 8 / 4 | |
| 3.0.0 | 8 / 4 | |
| 2.0.9 | 8 / 4 | |
| 2.0.8 | 8 / 4 | |
| 2.0.7 | 8 / 4 | |
| 2.0.6 | 8 / 4 | |
| 2.0.5 | 8 / 8 | |
| 2.0.4 | 8 / 8 | |
| 2.0.3 | 8 / 8 | |
| 2.0.1 | 8 / 8 | |
| 2.0.0 | 8 / 8 | |
| 1.2.1 | 7 / 8 | |
| 1.2.0 | 7 / 8 | |
| 1.1.0 | 7 / 8 | |
| 1.0.3 | 7 / 8 | |
| 1.0.2 | 7 / 8 | |
| 1.0.1 | 7 / 8 | |
| 1.0.0 | 7 / 8 | |
| 0.3.0 | 7 / 8 | |
| 0.2.1 | 7 / 7 | |
| 0.2.0 | 7 / 7 | |
| 0.1.2 | 7 / 6 | |
| 0.1.1 | 7 / 6 | |
| 0.1.0 | 7 / 6 | |
| 0.0.3 | 7 / 6 | |
| 0.0.2 | 8 / 6 | |
| 0.0.1 | 6 / 6 | |
| 0.0.0 | 5 / 6 |
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-02-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.