bare-worker
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transfer from kasperisager to mafintosh is a known Holepunch org transition; mafintosh is the org founder. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA attestation; consistent with org-level CI publishing setup. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mafintosh added as maintainer is expected for Holepunch org ownership consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager removal is part of the same legitimate org transition. | ai | |
| provenance | no-provenance | AI (provenance): Holepunch packages consistently lack provenance; stable false positive for this publisher. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Intentional preload mechanism in a worker thread library; stable pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.1.9 | 4 / 4 | |
| 4.1.8 | 4 / 4 | |
| 4.1.6 | 4 / 3 | |
| 4.1.5 | 4 / 3 | |
| 4.1.3 | 4 / 3 | |
| 4.1.1 | 4 / 3 | |
| 4.1.0 | 4 / 3 | |
| 4.0.0 | 5 / 3 |
v4.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.8
3 findingsAll previous maintainers (kasperisager) were replaced by new maintainers (mafintosh). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2026-05-27. 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.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.