@duckcodeailabs/dql-governance
DQL Governance: block testing, certification, cost estimation, and access policies
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo publish pattern; no behavioral change, consistent across sibling packages. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Coordinated monorepo release cadence, not indicative of compromise. | ai | |
| phantom-deps | phantom-dep:@duckcodeailabs/dql-core | AI (phantom-deps): Sibling monorepo package from the same org scope; declared as a dependency for type resolution or re-export purposes without direct import is a common monorepo pattern. | ai |
Versions (showing 28 of 128)
| Version | Deps | Published |
|---|---|---|
| 0.8.16 | 2 / 2 | |
| 0.8.15 | 2 / 2 | |
| 0.8.14 | 2 / 2 | |
| 0.8.13 | 2 / 2 | |
| 0.8.12 | 2 / 2 | |
| 0.8.11 | 2 / 2 | |
| 0.8.10 | 2 / 2 | |
| 0.8.9 | 2 / 2 | |
| 0.8.8 | 2 / 2 | |
| 0.8.7 | 2 / 2 | |
| 0.8.6 | 2 / 2 | |
| 0.8.5 | 2 / 2 | |
| 0.8.4 | 2 / 2 | |
| 0.8.3 | 2 / 2 | |
| 0.8.2 | 2 / 2 | |
| 0.8.1 | 2 / 2 | |
| 0.8.0 | 2 / 2 | |
| 0.7.1 | 2 / 2 | |
| 0.7.0 | 2 / 2 | |
| 0.6.0 | 2 / 2 | |
| 0.1.7 | 2 / 2 | |
| 0.1.6 | 2 / 2 | |
| 0.1.5 | 2 / 2 | |
| 0.1.4 | 2 / 2 | |
| 0.1.3 | 2 / 2 | |
| 0.1.2 | 2 / 2 | |
| 0.1.1 | 2 / 2 | |
| 0.1.0 | 2 / 2 |
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.