conventional-changelog-ember
Ember 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): conventional-changelog-ember is a legitimate preset in the official conventional-changelog monorepo. Templated naming and no-deps are expected characteristics of this package family, not spam indicators. | ai | |
| provenance | missing-githead | AI (provenance): Package is part of the well-established conventional-changelog monorepo published by oss-bot. Missing gitHead reflects a CI/CD environment change, not a security concern for this trusted publisher. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 0 | |
| 4.0.0 | 0 / 0 | |
| 3.0.0 | 0 / 0 | |
| 2.0.9 | 1 / 0 | |
| 2.0.8 | 1 / 0 | |
| 2.0.4 | 1 / 0 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 4 | |
| 2.0.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.3.12 | 1 / 4 | |
| 0.3.11 | 1 / 4 | |
| 0.3.10 | 1 / 4 | |
| 0.3.9 | 1 / 4 | |
| 0.3.8 | 1 / 4 | |
| 0.3.7 | 1 / 4 | |
| 0.3.6 | 1 / 4 | |
| 0.3.5 | 1 / 9 | |
| 0.3.4 | 1 / 9 | |
| 0.3.3 | 1 / 9 | |
| 0.3.2 | 1 / 9 | |
| 0.3.1 | 1 / 9 | |
| 0.3.0 | 1 / 9 | |
| 0.2.10 | 1 / 9 | |
| 0.2.9 | 1 / 9 | |
| 0.2.8 | 1 / 9 | |
| 0.2.7 | 1 / 9 | |
| 0.2.6 | 1 / 9 | |
| 0.2.5 | 1 / 9 | |
| 0.2.4 | 1 / 9 | |
| 0.2.3 | 1 / 9 | |
| 0.2.2 | 1 / 10 | |
| 0.2.1 | 1 / 10 | |
| 0.2.0 | 1 / 10 | |
| 0.1.0 | 1 / 10 | |
| 0.0.0 | 1 / 8 |
v5.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.