@logto/client
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:camelcase-keys | AI (phantom-deps): camelcase-keys is a declared runtime dependency; phantom-dep false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 4 / 11 | |
| 3.1.7 | 4 / 11 | |
| 3.1.6 | 4 / 11 | |
| 3.1.5 | 4 / 11 | |
| 3.1.4 | 4 / 11 | |
| 3.1.3 | 4 / 11 | |
| 3.1.2 | 4 / 11 | |
| 3.1.1 | 4 / 11 | |
| 3.0.4 | 4 / 11 | |
| 3.0.3 | 4 / 11 |
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.