← Home

conventional-commits-filter

Filter out reverted commits parsed by conventional-commits-parser.

20
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

bcoeoss-botstevemaotapppi

Keywords

filterconventionalchangelogcommits

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Well-established package in conventional-changelog ecosystem; 6.7M weekly downloads; signals are false positives. ai
provenance missing-githead AI (provenance): Trusted publisher oss-bot; missing gitHead reflects publish tooling change, not a security concern for this package. ai

Versions (showing 20 of 20)

Version Deps Published
5.0.0 0 / 0
4.0.0 0 / 0
3.0.0 2 / 0
2.0.7 2 / 0
2.0.6 2 / 0
2.0.2 2 / 0
2.0.1 2 / 0
2.0.0 2 / 0
1.1.6 2 / 0
1.1.5 2 / 0
1.1.4 2 / 4
1.1.3 2 / 4
1.1.2 2 / 4
1.1.1 2 / 4
1.1.0 2 / 4
1.0.0 2 / 5
0.1.1 2 / 5
0.1.0 2 / 5
0.0.1 2 / 5
0.0.0 2 / 5

v4.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.