@arethetypeswrong/core
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): Moved from personal npm publish to GitHub Actions CI/CD; SLSA provenance confirms legitimate pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 406k downloads; dormancy consistent with toolchain migration (tsc→tsgo). | ai | |
| source-diff | obfuscated-file:dist/internal/minimalLibDts.d.ts | AI (source-diff): Embedded TS lib .d.ts content string; expected for a TypeScript analysis tool. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @arethetypeswrong/core is not a typosquat of cors; edit-distance match is spurious. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package; missing keywords and terse README are normal for monorepo sub-packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.18.4 | 8 / 4 | |
| 0.18.3 | 8 / 4 | |
| 0.18.2 | 8 / 4 | |
| 0.18.1 | 8 / 4 | |
| 0.18.0 | 8 / 4 | |
| 0.17.4 | 8 / 4 | |
| 0.17.3 | 7 / 4 | |
| 0.17.2 | 7 / 4 | |
| 0.17.1 | 7 / 4 | |
| 0.17.0 | 7 / 4 | |
| 0.16.4 | 7 / 4 | |
| 0.16.2 | 7 / 4 | |
| 0.16.0 | 7 / 4 |
v0.18.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.