bower-endpoint-parser
Little module that helps with endpoints parsing.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change (satazor → sheerun) occurred in 2014 as part of a legitimate Bower project maintainer transition. sheerun has 189 approved packages and is a known Bower ecosystem contributor. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (paulirish, sindresorhus, sheerun, wibblymat) are all well-known, reputable JS ecosystem developers added during the 2014 Bower project transition. Clearly legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy and 2014 publish align with the Bower project maintainer transition. No malicious indicators; package is 10+ years old with clean history since. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2014, predating Sigstore provenance. Not a meaningful risk signal for this package. | ai |
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2014-06-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.