@privy-io/js-sdk-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:set-cookie-parser | AI (phantom-deps): set-cookie-parser is a declared runtime dependency; phantom-dep is a false positive for this package. | ai |
Versions (showing 100 of 185)
| Version | Deps | Published |
|---|---|---|
| 0.68.4 | 13 / 32 | |
| 0.68.3 | 13 / 32 | |
| 0.68.2 | 13 / 32 | |
| 0.68.1 | 13 / 32 | |
| 0.68.0 | 13 / 32 | |
| 0.67.4 | 13 / 32 | |
| 0.67.3 | 13 / 32 | |
| 0.67.2 | 13 / 32 | |
| 0.67.1 | 13 / 32 | |
| 0.67.0 | 13 / 32 | |
| 0.66.0 | 13 / 32 | |
| 0.65.4 | 13 / 32 | |
| 0.65.3 | 13 / 32 | |
| 0.65.2 | 13 / 32 | |
| 0.65.1 | 13 / 32 | |
| 0.65.0 | 13 / 32 | |
| 0.64.0 | 13 / 32 | |
| 0.63.0 | 13 / 32 | |
| 0.62.0 | 13 / 32 | |
| 0.61.3 | 14 / 33 | |
| 0.61.2 | 14 / 33 | |
| 0.61.1 | 14 / 33 | |
| 0.61.0 | 14 / 32 | |
| 0.60.9 | 13 / 32 | |
| 0.60.8 | 13 / 32 | |
| 0.60.7 | 13 / 32 | |
| 0.60.1 | 13 / 32 | |
| 0.59.0 | 13 / 32 | |
| 0.58.7 | 13 / 32 | |
| 0.58.6 | 13 / 32 | |
| 0.58.5 | 13 / 32 | |
| 0.58.4 | 13 / 32 | |
| 0.58.3 | 13 / 32 | |
| 0.58.2 | 13 / 30 | |
| 0.58.1 | 13 / 30 | |
| 0.58.0 | 13 / 28 | |
| 0.57.1 | 12 / 28 | |
| 0.57.0 | 12 / 28 | |
| 0.56.5 | 12 / 28 | |
| 0.56.4 | 12 / 28 | |
| 0.56.3 | 12 / 28 | |
| 0.56.2 | 12 / 28 | |
| 0.56.1 | 12 / 28 | |
| 0.56.0 | 12 / 28 | |
| 0.55.4 | 12 / 28 | |
| 0.55.3 | 12 / 28 | |
| 0.55.2 | 17 / 24 | |
| 0.55.1 | 17 / 24 | |
| 0.55.0 | 17 / 24 | |
| 0.54.2 | 17 / 24 | |
| 0.54.1 | 17 / 24 | |
| 0.54.0 | 17 / 24 | |
| 0.53.4 | 17 / 24 | |
| 0.53.3 | 17 / 24 | |
| 0.53.2 | 17 / 24 | |
| 0.53.1 | 17 / 24 | |
| 0.53.0 | 17 / 24 | |
| 0.52.10 | 17 / 24 | |
| 0.52.9 | 17 / 24 | |
| 0.52.8 | 17 / 24 | |
| 0.52.7 | 17 / 24 | |
| 0.52.6 | 17 / 24 | |
| 0.52.5 | 17 / 24 | |
| 0.52.4 | 17 / 24 | |
| 0.52.3 | 17 / 24 | |
| 0.52.2 | 17 / 24 | |
| 0.52.1 | 17 / 24 | |
| 0.52.0 | 17 / 24 | |
| 0.51.1 | 17 / 24 | |
| 0.51.0 | 17 / 24 | |
| 0.50.11 | 17 / 24 | |
| 0.50.10 | 17 / 24 | |
| 0.50.9 | 17 / 24 | |
| 0.50.8 | 17 / 24 | |
| 0.50.7 | 17 / 24 | |
| 0.50.6 | 17 / 24 | |
| 0.50.5 | 17 / 24 | |
| 0.50.4 | 17 / 24 | |
| 0.50.3 | 17 / 24 | |
| 0.50.2 | 17 / 24 | |
| 0.50.1 | 17 / 24 | |
| 0.50.0 | 17 / 24 | |
| 0.49.0 | 17 / 24 | |
| 0.48.2 | 17 / 24 | |
| 0.48.1 | 17 / 24 | |
| 0.48.0 | 17 / 24 | |
| 0.47.3 | 17 / 24 | |
| 0.47.2 | 17 / 24 | |
| 0.47.1 | 17 / 24 | |
| 0.47.0 | 17 / 24 | |
| 0.46.4 | 17 / 24 | |
| 0.46.3 | 17 / 24 | |
| 0.46.2 | 17 / 24 | |
| 0.46.1 | 15 / 24 | |
| 0.46.0 | 15 / 24 | |
| 0.45.1 | 15 / 24 | |
| 0.45.0 | 15 / 24 | |
| 0.44.4 | 15 / 23 | |
| 0.44.3 | 15 / 23 | |
| 0.44.2 | 15 / 23 |
v0.68.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.