@paralleldrive/cuid2
[](https://github.com/paralleldrive/aidd)[](https://paralleldrive.com)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): cuid2 is a well-known, distinct unique-ID library by Eric Elliott; name similarity to 'uuid' is coincidental, not typosquatting. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 3 / 16 | |
| 3.2.0 | 3 / 15 | |
| 3.1.0 | 3 / 15 | |
| 3.0.6 | 3 / 15 | |
| 3.0.5 | 3 / 15 | |
| 3.0.4 | 3 / 15 | |
| 3.0.2 | 3 / 15 | |
| 3.0.1 | 3 / 15 | |
| 3.0.0 | 2 / 15 | |
| 2.3.1 | 1 / 14 | |
| 2.3.0 | 2 / 15 | |
| 2.2.2 | 1 / 14 | |
| 2.2.1 | 1 / 14 | |
| 2.2.0 | 1 / 14 | |
| 2.1.0 | 1 / 14 | |
| 2.0.1 | 1 / 14 | |
| 2.0.0 | 1 / 14 | |
| 1.0.2 | 1 / 14 | |
| 1.0.1 | 1 / 14 | |
| 1.0.0 | 1 / 14 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.