@origintrail-official/dkg-publisher
Publishing protocol for DKG V9. Handles the complete lifecycle of getting Knowledge Assets from a node into the network — from RDF processing through Merkle tree construction to on-chain finalization.
1
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
branarakicnikita_abrashkin
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:n3 | AI (phantom-deps): Transitive/config-level usage in RDF-processing monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:rdf-canonize | AI (phantom-deps): Same as n3 — RDF tooling used indirectly via sibling packages. | ai | |
| phantom-deps | phantom-dep:@multiformats/multiaddr | AI (phantom-deps): Peer/transitive usage in DKG networking layer; stable false positive. | ai | |
| phantom-deps | phantom-dep:@origintrail-official/dkg-query | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo deps. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.1 | 8 / 2 |
v0.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.