@elizaos/client-direct
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the @elizaos monorepo; missing metadata (description, repo URL, keywords) is a common pattern for scoped monorepo packages, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo scoped package; missing description is a cosmetic gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@types/cors | AI (phantom-deps): Framework-scoped type definition; phantom dep finding is expected for @types/* packages in monorepo setups. | ai | |
| phantom-deps | phantom-dep:@types/body-parser | AI (phantom-deps): Framework-scoped type definition; phantom dep finding is expected for @types/* packages in monorepo setups. | ai | |
| phantom-deps | phantom-dep:path-to-regexp | AI (phantom-deps): Referenced in config files per the finding; not a security concern for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.25.9 | 10 / 3 |
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.