bare-module-lexer
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 to mafintosh (Holepunch founder) is a known legitimate org-level ownership consolidation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mafintosh is the Holepunch org owner; addition is expected for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager removal is part of the same legitimate org consolidation. | ai | |
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions publisher aligns with SLSA provenance attestation; CI/CD publishing is expected. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt native addon binaries (.bare) for multiple platforms; consistent with addon:true and CMakeLists.txt build system. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.6.3 | 1 / 8 | |
| 1.6.2 | 1 / 8 | |
| 1.6.1 | 1 / 8 | |
| 1.6.0 | 1 / 8 | |
| 1.5.3 | 1 / 8 | |
| 1.5.2 | 1 / 8 | |
| 1.5.1 | 1 / 8 | |
| 1.5.0 | 1 / 9 | |
| 1.4.7 | 1 / 8 | |
| 1.4.6 | 1 / 8 | |
| 1.4.5 | 1 / 8 | |
| 1.4.4 | 1 / 8 | |
| 1.4.3 | 1 / 8 | |
| 1.4.2 | 1 / 8 | |
| 1.4.1 | 1 / 8 | |
| 1.4.0 | 1 / 8 | |
| 1.3.0 | 1 / 8 | |
| 1.2.2 | 1 / 8 | |
| 1.2.1 | 1 / 8 | |
| 1.2.0 | 1 / 8 | |
| 1.1.0 | 1 / 6 | |
| 1.0.7 | 1 / 6 | |
| 1.0.6 | 1 / 6 | |
| 1.0.5 | 1 / 6 | |
| 1.0.4 | 1 / 6 | |
| 1.0.3 | 0 / 3 | |
| 1.0.2 | 0 / 3 | |
| 1.0.1 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v1.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.