@origintrail-official/dkg-query
SPARQL query engine for DKG V9. Provides paranet-scoped querying, Knowledge Asset resolution by UAL, and read-only query validation.
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 | no-provenance | AI (provenance): Consistent across all @origintrail-official packages; org hasn't adopted Sigstore attestation yet. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 10.0.9 | 2 / 2 | |
| 10.0.8 | 2 / 2 | |
| 10.0.7 | 2 / 2 | |
| 10.0.6 | 2 / 2 | |
| 10.0.5 | 2 / 2 | |
| 10.0.4 | 2 / 2 | |
| 10.0.3 | 2 / 2 | |
| 10.0.2 | 2 / 2 | |
| 10.0.1 | 2 / 2 | |
| 10.0.0 | 2 / 2 | |
| 0.0.1 | 2 / 2 |
v10.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jurij89) than the most recent previously approved version (branarakic) on unknown date, but jurij89 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.