@agentvault/agentvault
The security infrastructure layer for AI agents -- cryptographic identity, earned trust, and Signal-grade encrypted communications natively integrated with [OpenClaw](https://openclaw.ai).
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/openclaw-entry.js | AI (source-diff): Same libsodium WASM binary data pattern; benign crypto library bundling. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): MCP SDK is bundled into dist; phantom-dep heuristic misses bundled imports. | ai | |
| source-diff | encoded-string-file:dist/cli.js | AI (source-diff): Base64 strings are libsodium WASM binary data bundled via libsodium-wrappers-sumo; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same libsodium WASM bundle pattern; not a malicious payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase caused by bundling libsodium-wrappers-sumo WASM; expected for this package. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dependency used in the bundled dist output; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 9 of 209)
| Version | Deps | Published |
|---|---|---|
| 0.9.7 | 1 / 8 | |
| 0.9.6 | 1 / 8 | |
| 0.9.5 | 1 / 8 | |
| 0.9.4 | 1 / 8 | |
| 0.9.3 | 1 / 8 | |
| 0.9.2 | 1 / 8 | |
| 0.9.1 | 1 / 8 | |
| 0.9.0 | 1 / 8 | |
| 0.8.0 | 1 / 8 |
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.