bare-net
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Holepunchto org migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate pipeline origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of kasperisager reflects org-level CI publishing transition, not a takeover; corroborated by SLSA attestation. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 4 / 4 | |
| 2.3.1 | 4 / 3 | |
| 2.2.3 | 4 / 3 | |
| 2.2.2 | 4 / 3 | |
| 2.2.1 | 4 / 3 | |
| 2.2.0 | 4 / 3 | |
| 2.1.1 | 4 / 3 | |
| 2.1.0 | 4 / 3 | |
| 2.0.2 | 4 / 3 |
v2.3.2
2 findingsThis version was published by a different npm account than previous versions on 2026-06-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.