@ydbjs/query
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): First-party sibling package from same ydb-platform org/monorepo. | ai | |
| dependencies | unvetted-dep:@ydbjs/core | AI (dependencies): First-party sibling package from same ydb-platform org/monorepo. | ai | |
| dependencies | unvetted-dep:@ydbjs/error | AI (dependencies): First-party sibling package from same ydb-platform org/monorepo. | ai | |
| dependencies | unvetted-dep:@ydbjs/retry | AI (dependencies): First-party sibling package from same ydb-platform org/monorepo. | ai | |
| dependencies | unvetted-dep:@ydbjs/value | AI (dependencies): First-party sibling package from same ydb-platform org/monorepo. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is a declared runtime dependency; phantom-dep fires on config-file reference, stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 10 / 1 | |
| 6.1.0 | 10 / 1 | |
| 6.0.5 | 9 / 1 | |
| 6.0.4 | 9 / 1 | |
| 6.0.3 | 9 / 1 | |
| 6.0.2 | 9 / 1 | |
| 6.0.1 | 9 / 1 | |
| 6.0.0 | 9 / 1 |
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.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Published 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.