@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 100 of 209)
| Version | Deps | Published |
|---|---|---|
| 0.23.11 | 2 / 8 | |
| 0.23.10 | 2 / 8 | |
| 0.23.9 | 2 / 8 | |
| 0.23.8 | 2 / 8 | |
| 0.23.7 | 2 / 8 | |
| 0.23.6 | 2 / 8 | |
| 0.23.5 | 2 / 8 | |
| 0.23.4 | 2 / 8 | |
| 0.23.3 | 2 / 8 | |
| 0.23.2 | 2 / 8 | |
| 0.23.1 | 2 / 8 | |
| 0.23.0 | 2 / 8 | |
| 0.22.0 | 2 / 8 | |
| 0.21.7 | 2 / 8 | |
| 0.21.5 | 2 / 8 | |
| 0.21.4 | 2 / 8 | |
| 0.21.3 | 2 / 8 | |
| 0.21.2 | 2 / 8 | |
| 0.21.1 | 2 / 8 | |
| 0.21.0 | 2 / 8 | |
| 0.20.43 | 2 / 8 | |
| 0.20.42 | 2 / 8 | |
| 0.20.41 | 2 / 8 | |
| 0.20.40 | 2 / 8 | |
| 0.20.39 | 2 / 8 | |
| 0.20.38 | 2 / 8 | |
| 0.20.37 | 2 / 8 | |
| 0.20.36 | 2 / 8 | |
| 0.20.35 | 2 / 8 | |
| 0.20.34 | 2 / 8 | |
| 0.20.33 | 2 / 8 | |
| 0.20.32 | 2 / 8 | |
| 0.20.31 | 2 / 8 | |
| 0.20.30 | 2 / 8 | |
| 0.20.29 | 2 / 8 | |
| 0.20.28 | 2 / 8 | |
| 0.20.27 | 2 / 8 | |
| 0.20.26 | 2 / 8 | |
| 0.20.25 | 2 / 8 | |
| 0.20.24 | 2 / 8 | |
| 0.20.23 | 2 / 8 | |
| 0.20.22 | 2 / 8 | |
| 0.20.21 | 2 / 8 | |
| 0.20.20 | 2 / 8 | |
| 0.20.19 | 2 / 8 | |
| 0.20.18 | 2 / 8 | |
| 0.20.17 | 2 / 8 | |
| 0.20.16 | 2 / 8 | |
| 0.20.15 | 2 / 8 | |
| 0.20.14 | 2 / 8 | |
| 0.20.13 | 2 / 8 | |
| 0.20.12 | 2 / 8 | |
| 0.20.11 | 2 / 8 | |
| 0.20.10 | 2 / 8 | |
| 0.20.9 | 2 / 8 | |
| 0.20.8 | 2 / 8 | |
| 0.20.7 | 2 / 8 | |
| 0.20.6 | 2 / 8 | |
| 0.20.5 | 2 / 8 | |
| 0.20.4 | 2 / 8 | |
| 0.20.3 | 2 / 8 | |
| 0.20.2 | 2 / 8 | |
| 0.20.1 | 2 / 8 | |
| 0.20.0 | 2 / 8 | |
| 0.19.71 | 2 / 8 | |
| 0.19.70 | 2 / 8 | |
| 0.19.69 | 2 / 8 | |
| 0.19.68 | 2 / 8 | |
| 0.19.67 | 2 / 8 | |
| 0.19.66 | 2 / 8 | |
| 0.19.65 | 2 / 8 | |
| 0.19.64 | 2 / 8 | |
| 0.19.63 | 2 / 8 | |
| 0.19.62 | 2 / 8 | |
| 0.19.61 | 2 / 8 | |
| 0.19.60 | 2 / 8 | |
| 0.19.59 | 2 / 8 | |
| 0.19.58 | 2 / 8 | |
| 0.19.57 | 2 / 8 | |
| 0.19.56 | 2 / 8 | |
| 0.19.55 | 2 / 8 | |
| 0.19.54 | 2 / 8 | |
| 0.19.53 | 2 / 8 | |
| 0.19.52 | 2 / 8 | |
| 0.19.51 | 2 / 8 | |
| 0.19.50 | 2 / 8 | |
| 0.19.49 | 2 / 8 | |
| 0.19.48 | 2 / 8 | |
| 0.19.47 | 2 / 8 | |
| 0.19.46 | 2 / 8 | |
| 0.19.45 | 2 / 8 | |
| 0.19.44 | 2 / 8 | |
| 0.19.43 | 2 / 8 | |
| 0.19.42 | 2 / 8 | |
| 0.19.41 | 2 / 8 | |
| 0.19.40 | 2 / 8 | |
| 0.19.39 | 2 / 8 | |
| 0.19.38 | 2 / 8 | |
| 0.19.37 | 2 / 8 | |
| 0.19.36 | 2 / 8 |
v0.23.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.