conventional-changelog-angular
Angular 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@conventional-changelog/template | AI (dependencies): First-party dep from the same conventional-changelog monorepo; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established package with trusted bot publisher and strong approval history; lack of Sigstore attestation is a best-practice gap, not a security risk for this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 9.2.1 | 1 / 0 | |
| 9.2.0 | 1 / 0 | |
| 9.1.0 | 1 / 0 | |
| 9.0.0 | 1 / 0 | |
| 8.3.1 | 1 / 0 | |
| 8.3.0 | 1 / 0 | |
| 8.2.0 | 1 / 0 | |
| 8.1.0 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.0.13 | 2 / 0 | |
| 5.0.12 | 2 / 0 | |
| 5.0.11 | 2 / 0 | |
| 5.0.10 | 2 / 0 | |
| 5.0.6 | 2 / 0 | |
| 5.0.5 | 2 / 0 | |
| 5.0.3 | 2 / 0 | |
| 5.0.2 | 2 / 0 | |
| 5.0.1 | 2 / 5 | |
| 5.0.0 | 2 / 5 | |
| 4.0.1 | 2 / 5 | |
| 4.0.0 | 2 / 5 | |
| 3.0.7 | 2 / 5 | |
| 3.0.6 | 2 / 5 | |
| 3.0.5 | 2 / 5 | |
| 3.0.4 | 2 / 5 | |
| 3.0.3 | 2 / 5 | |
| 3.0.2 | 2 / 5 | |
| 3.0.1 | 2 / 5 | |
| 3.0.0 | 2 / 5 | |
| 1.6.6 | 2 / 5 | |
| 1.6.5 | 2 / 10 | |
| 1.6.4 | 2 / 10 | |
| 1.6.3 | 2 / 10 | |
| 1.6.2 | 2 / 10 | |
| 1.6.1 | 2 / 10 | |
| 1.6.0 | 2 / 10 | |
| 1.5.3 | 2 / 10 | |
| 1.5.2 | 2 / 10 | |
| 1.5.1 | 2 / 10 | |
| 1.5.0 | 2 / 10 | |
| 1.4.0 | 4 / 10 | |
| 1.3.4 | 3 / 10 | |
| 1.3.3 | 3 / 10 | |
| 1.3.2 | 3 / 10 | |
| 1.3.1 | 3 / 10 | |
| 1.3.0 | 3 / 10 | |
| 1.2.0 | 3 / 10 | |
| 1.1.0 | 3 / 10 | |
| 1.0.0 | 2 / 10 |
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dangreen.
This version was published by a different npm account than previous versions on 2025-10-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.