bare-module-lexer
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.4.7
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-module-lexer.bare • prebuilds/android-arm64/bare-module-lexer.bare • prebuilds/android-ia32/bare-module-lexer.bare • prebuilds/android-x64/bare-module-lexer.bare • prebuilds/darwin-arm64/bare-module-lexer.bare • prebuilds/darwin-x64/bare-module-lexer.bare • prebuilds/ios-arm64-simulator/bare-module-lexer.bare • prebuilds/ios-arm64/bare-module-lexer.bare • prebuilds/ios-x64-simulator/bare-module-lexer.bare • prebuilds/linux-arm64/bare-module-lexer.bare ... and 13 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.