@bhsd/browser
13
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
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): Package has legitimate repo, tooling, and approved dependents; 0.0.0 reflects initial release, not throwaway malware. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 5 | |
| 1.1.0 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.5.0 | 0 / 6 | |
| 0.4.0 | 0 / 8 | |
| 0.3.2 | 0 / 8 | |
| 0.3.1 | 0 / 8 | |
| 0.3.0 | 0 / 17 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 | |
| 0.1.0 | 0 / 17 | |
| 0.0.1 | 0 / 17 | |
| 0.0.0 | 0 / 17 |
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.