conventional-changelog-conventionalcommits
Conventionalcommits.org preset for conventional-changelog.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dangreen is an established publisher (603 approved packages) taking over from oss-bot; consistent with a legitimate maintainer transition in the conventional-changelog org. | ai | |
| provenance | no-provenance | AI (provenance): Established package in the conventional-changelog org; lack of provenance is a minor hygiene issue, not a security risk for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.3.1 | 1 / 0 | |
| 9.3.0 | 1 / 0 | |
| 9.2.0 | 1 / 0 | |
| 9.1.0 | 1 / 0 | |
| 9.0.0 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.0.2 | 1 / 0 | |
| 7.0.1 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.1.0 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.6.3 | 3 / 0 | |
| 4.6.2 | 3 / 0 | |
| 4.6.1 | 3 / 0 | |
| 4.6.0 | 3 / 0 | |
| 4.5.0 | 3 / 0 | |
| 4.4.0 | 3 / 0 | |
| 4.3.1 | 3 / 0 | |
| 4.3.0 | 3 / 0 | |
| 4.2.3 | 3 / 0 | |
| 4.2.2 | 3 / 0 | |
| 4.2.1 | 3 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.0.0 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 2 / 0 |
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-10. 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.
v9.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-19. 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.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.