← Home

@ajna-inc/vaults

npm

Post-quantum encrypted vaults with DIDComm protocol for Credo. Client-side encryption using ML-KEM-768, AES-256-GCM, and Shamir secret sharing with P2P sharing via DIDComm messages.

20
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

vinaysingh8866

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): wasm-bindgen compiled crypto module matches declared crypto deps, not a backdoor. ai
source-diff net-exec-file:build/index.rn.mjs AI (source-diff): Bundled React Native build artifact using @noble/* crypto libs; standard rolldown boilerplate, not dropper malware. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get in wasm-bindgen generated JS glue code; not obfuscation. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function in wasm-bindgen generated JS glue code; standard pattern for WASM string interop. ai

Versions (showing 20 of 20)

Version Deps Published
0.7.4 10 / 2
0.7.3 9 / 2
0.7.2 9 / 2
0.7.1 9 / 2
0.7.0 9 / 2
0.6.3 7 / 2
0.6.2 7 / 2
0.6.1 7 / 2
0.5.0 9 / 6
0.2.5 8 / 6
0.2.4 8 / 6
0.2.3 8 / 6
0.2.2 8 / 6
0.2.1 8 / 6
0.2.0 8 / 6
0.1.4 6 / 6
0.1.3 6 / 6
0.1.2 6 / 6
0.1.1 6 / 6
0.1.0 6 / 5

v0.7.4

2 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • build/wasm/vault_crypto_bg.wasm • wasm/vault_crypto_bg.wasm

LOW No provenance attestation provenance

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