@ucanto/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 UCAN library; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 10.4.6 | 5 / 9 | |
| 10.4.5 | 5 / 9 | |
| 10.4.2 | 5 / 9 | |
| 10.4.0 | 5 / 9 | |
| 10.3.1 | 5 / 9 | |
| 10.3.0 | 5 / 9 | |
| 10.2.1 | 5 / 9 | |
| 10.2.0 | 5 / 9 | |
| 10.1.1 | 5 / 9 | |
| 10.1.0 | 5 / 9 |
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.