@certd/jdcloud
jdcloud openApi sdk
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:uuid | AI (phantom-deps): UUID is a core SDK dependency; phantom-dep heuristic misses indirect imports. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Debug is a build/logging dependency; referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): Rollup is the build tool; correctly declared as dependency for build scripts. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Node-fetch is a core SDK dependency for HTTP requests; indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:create-hash | AI (phantom-deps): Create-hash is a core SDK dependency; phantom-dep heuristic misses indirect imports. | ai | |
| phantom-deps | phantom-dep:create-hmac | AI (phantom-deps): Create-hmac is a core SDK dependency; phantom-dep heuristic misses indirect imports. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 1.34.7 | 10 / 12 | |
| 1.34.6 | 10 / 12 | |
| 1.34.5 | 10 / 12 | |
| 1.34.4 | 10 / 12 | |
| 1.34.3 | 10 / 12 | |
| 1.34.2 | 10 / 12 | |
| 1.34.1 | 10 / 12 | |
| 1.34.0 | 10 / 12 | |
| 1.33.8 | 10 / 12 | |
| 1.33.7 | 10 / 12 | |
| 1.33.6 | 10 / 12 | |
| 1.33.5 | 10 / 12 | |
| 1.33.4 | 10 / 12 | |
| 1.33.3 | 10 / 12 | |
| 1.33.2 | 10 / 12 | |
| 1.33.1 | 10 / 12 | |
| 1.33.0 | 10 / 12 | |
| 1.32.0 | 10 / 12 | |
| 1.31.11 | 10 / 12 | |
| 1.31.10 | 10 / 12 |
v1.33.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.