← Home

@origintrail-official/dkg-adapter-elizaos

npm Repository Homepage

ElizaOS plugin adapter — turns any ElizaOS agent into a DKG V9 node

11
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

branarakicjurij89

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@origintrail-official/dkg-core AI (phantom-deps): Same-org monorepo sibling; may be re-exported transitively rather than directly imported. ai
phantom-deps phantom-dep:@origintrail-official/dkg-storage AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for transitive re-exports. ai

Versions (showing 11 of 11)

Version Deps Published
10.0.9 1 / 2
10.0.8 1 / 2
10.0.7 1 / 2
10.0.6 1 / 2
10.0.5 1 / 2
10.0.4 1 / 2
10.0.3 1 / 2
10.0.2 1 / 2
10.0.1 1 / 2
10.0.0 1 / 2
0.0.1 3 / 2

v10.0.9

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jurij89 → branarakic (on 2026-07-21, known maintainer) provenance

This version was published by a different npm account (branarakic) than the most recent previously approved version (jurij89) on 2026-07-21, but branarakic 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.8

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: branarakic → jurij89 (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (jurij89) than the most recent previously approved version (branarakic) on 2026-07-17, 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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.