@yarn-tool/changelog
Generate and update CHANGELOG.md using conventional commits for monorepo workspaces
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@bluelovers/conventional-changelog-bluelovers | AI (phantom-deps): Declared as peer dep and listed in dependencies; phantom-dep heuristic fires on config-only reference, not a real concern for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.13 | 14 / 0 | |
| 3.0.12 | 14 / 0 | |
| 3.0.11 | 14 / 0 | |
| 3.0.10 | 14 / 0 | |
| 3.0.7 | 14 / 0 | |
| 3.0.6 | 14 / 0 | |
| 3.0.5 | 14 / 0 | |
| 3.0.4 | 15 / 0 | |
| 3.0.3 | 15 / 0 | |
| 3.0.2 | 15 / 0 | |
| 3.0.1 | 15 / 0 | |
| 3.0.0 | 15 / 0 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.