← Home

bower-registry-client

Provides easy interaction with the Bower registry

9
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

satazorsvnltowibblymatsindresorhussheerunpaulirishdesandro

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:svenlito.com AI (email-domain): Package is 12+ years old under the official bower GitHub org (Twitter-authored). The stale maintainer email is a historical artifact; no install scripts or malicious code present across any version. ai
provenance publisher-changed AI (provenance): Publisher change to sheerun occurred in 2014 as a legitimate Bower project maintainer transition. sheerun has a strong track record and the package remains under the official bower GitHub org. ai
dependencies unvetted-dep:request AI (dependencies): The `request` package is a well-known, widely-used HTTP client in the Node.js ecosystem. Its use here is legitimate and expected for a Bower registry client. ai
maintainer-change maintainer-added AI (maintainer-change): desandro is a well-known, reputable open-source developer; addition to the Bower org package is a legitimate contributor change, not a suspicious takeover. ai
phantom-deps phantom-dep:rimraf AI (phantom-deps): rimraf is a legitimate utility dep used in cleanup operations; phantom detection is a false positive for this package. ai
provenance no-provenance AI (provenance): Package is 4670 days old and predates Sigstore provenance; absence is expected and not a security concern for this established package. ai

Versions (showing 9 of 9)

Version Deps Published
0.2.4 8 / 8
0.2.3 8 / 8
0.2.2 8 / 7
0.1.6 8 / 7
0.1.5 8 / 7
0.1.4 8 / 7
0.1.3 8 / 7
0.1.2 8 / 7
0.1.1 8 / 7

v0.2.4

1 finding
INFO No provenance attestation provenance

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

v0.2.3

3 findings
HIGH Unclaimed maintainer email domain: svenlito.com email-domain

Maintainer email '[email protected]' uses domain 'svenlito.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

INFO Publisher changed: sheerun → sindresorhus (on 2015-01-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-01-22. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.2

2 findings
HIGH Unclaimed maintainer email domain: svenlito.com email-domain

Maintainer email '[email protected]' uses domain 'svenlito.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.1.6

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: satazor → svnlto (on 2013-12-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2013-12-17. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.