@elizaos/agent
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
shawticusshakkernerd
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-bulk-read | AI (semgrep): Standard config pattern: reads env vars filtered by character-specific prefix for ElizaOS character settings. Not exfiltration. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is used in scripts and nodemonConfig exec commands, not via direct import. Legitimate usage pattern. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript type definitions package, loaded by convention via tsconfig, not via import. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.25.9 | 7 / 4 |
v0.25.9
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.