@open-pioneer/build-package
Implements partial compilation for Open Pioneer Trails packages.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is a declared runtime dependency used as a bundler binary; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@open-pioneer/build-support | AI (phantom-deps): Same-org dep declared in dependencies; indirect usage pattern is normal for build tooling. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 15 / 8 | |
| 4.1.2 | 15 / 8 | |
| 4.1.1 | 15 / 8 | |
| 4.1.0 | 15 / 8 | |
| 4.0.6 | 15 / 8 | |
| 4.0.5 | 15 / 8 | |
| 4.0.4 | 15 / 8 | |
| 4.0.3 | 15 / 8 | |
| 4.0.2 | 15 / 8 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.