bower-logger
The logger used in the various architecture components of Bower.
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 from satazor to wibblymat occurred in Jan 2014 as part of a legitimate Bower project maintainer transition. Over 11 years old; no risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): wibblymat and paulirish are well-known contributors to the Bower ecosystem; addition was a legitimate project transition in 2014. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2014, well before Sigstore provenance attestation was available. 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-01-14. 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.