conventional-changelog-jquery
JQuery 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 | missing-githead | AI (provenance): Package is a long-established conventional-changelog preset published by trusted oss-bot; missing gitHead reflects a CI/CD pipeline change, not a supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Trusted oss-bot publisher with strong track record; lack of Sigstore attestation is a process gap, not a security indicator for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects the conventional-changelog monorepo pattern of many similarly-named presets. No-deps is expected for a simple preset package. Not spam. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.0.0 | 0 / 0 | |
| 3.0.11 | 1 / 0 | |
| 3.0.10 | 1 / 0 | |
| 3.0.6 | 1 / 0 | |
| 3.0.4 | 1 / 0 | |
| 3.0.3 | 1 / 3 | |
| 3.0.2 | 1 / 3 | |
| 3.0.1 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.3.9 | 1 / 3 | |
| 1.3.8 | 1 / 3 | |
| 1.3.7 | 1 / 3 | |
| 1.3.6 | 1 / 3 | |
| 1.3.5 | 1 / 3 | |
| 1.3.4 | 1 / 3 | |
| 1.3.3 | 1 / 8 | |
| 1.3.2 | 1 / 8 | |
| 1.3.1 | 1 / 8 | |
| 1.3.0 | 1 / 8 | |
| 1.2.1 | 1 / 8 | |
| 1.2.0 | 1 / 8 | |
| 1.1.1 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.0 | 1 / 9 | |
| 0.2.0 | 1 / 9 | |
| 0.1.0 | 1 / 9 | |
| 0.0.0 | 2 / 8 |
v6.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.
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.