@arethetypeswrong/cli
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from andrewbranch to GitHub Actions CI/CD is legitimate; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by project cadence; SLSA attestation confirms legitimate CI publish. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @arethetypeswrong/cli is a legitimate, established tool; Levenshtein match to 'joi' is a false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.18.3 | 7 / 5 | |
| 0.18.2 | 7 / 5 | |
| 0.18.1 | 7 / 5 | |
| 0.18.0 | 7 / 5 | |
| 0.17.3 | 7 / 5 |
v0.18.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.