@ydbjs/retry
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ydbjs/api | AI (dependencies): Same-org monorepo sibling; risk tracks the parent SDK, not an independent concern. | ai | |
| dependencies | unvetted-dep:@ydbjs/debug | AI (dependencies): Same-org monorepo sibling; risk tracks the parent SDK, not an independent concern. | ai | |
| dependencies | unvetted-dep:@ydbjs/error | AI (dependencies): Same-org monorepo sibling; risk tracks the parent SDK, not an independent concern. | ai | |
| dependencies | unvetted-dep:@ydbjs/abortable | AI (dependencies): Same-org monorepo sibling; risk tracks the parent SDK, not an independent concern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 5 / 0 | |
| 6.2.0 | 5 / 0 | |
| 6.0.5 | 5 / 0 | |
| 6.0.4 | 5 / 0 | |
| 6.0.3 | 6 / 0 | |
| 6.0.2 | 6 / 0 | |
| 6.0.1 | 6 / 0 | |
| 6.0.0 | 6 / 0 |
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.