@newtype-os/cli
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall selects platform-specific prebuilt binary from 12 optional deps — standard native binary distribution pattern. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped org package @newtype-os/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.73 | 0 / 0 | |
| 0.0.72 | 0 / 0 | |
| 0.0.67 | 0 / 0 | |
| 0.0.22 | 0 / 0 | |
| 0.0.6 | 0 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
2 findingsScript: bun ./postinstall.mjs || node ./postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.