@factory/cli-linux-x64-baseline
Platform-specific binary for @factory/cli (linux x64 for older CPUs without AVX2)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Expected profile for platform-specific binary shim package. | ai | |
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publisher, not a suspicious account swap. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.177.0 | 0 / 0 | |
| 0.176.0 | 0 / 0 | |
| 0.175.1 | 0 / 0 | |
| 0.174.0 | 0 / 0 | |
| 0.173.0 | 0 / 0 | |
| 0.172.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.177.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.176.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.175.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.174.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.173.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.172.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.