@bhsd/lezer-abusefilter
12
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
bhsd
Keywords
mediawikilezer
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legitimate niche parser package; 0.0.0 reflects initial release, not malicious intent. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 2 / 13 | |
| 0.4.1 | 0 / 14 | |
| 0.4.0 | 0 / 14 | |
| 0.3.2 | 3 / 15 | |
| 0.3.1 | 3 / 25 | |
| 0.3.0 | 3 / 25 | |
| 0.2.1 | 2 / 25 | |
| 0.2.0 | 2 / 25 | |
| 0.1.2 | 2 / 25 | |
| 0.1.1 | 2 / 25 | |
| 0.1.0 | 2 / 23 | |
| 0.0.0 | 1 / 22 |
v0.5.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.