@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 |
|---|---|---|---|---|
| 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 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.18.2 | 8 / 4 | |
| 0.18.1 | 8 / 4 | |
| 0.18.0 | 8 / 4 | |
| 0.17.3 | 7 / 4 |
v0.18.2
2 findingsPackage name '@arethetypeswrong/core' is 1 edit(s) away from popular package 'cors'.
Package 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
2 findingsPackage name '@arethetypeswrong/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.