node-vault has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test node-vault?

On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.

Where is the evidence for node-vault?

All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

node-vault

Client for HashiCorp's Vault

Not yet testedsource: GitHub homepageJavaScriptMITcommit bd429e885926

JavaScript, MIT licensed. The project labels itself: api, api client, client, hashicorp, node, node vault, nodejs and secrets.

node-vault has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict: Not yet tested
Argusic Score: not scored yet
recorded runs: 0
last tested: -
stars: 556
forks: 160
open issues: 15
watchers: 7
size: 1 MB
created: 2015-04-29
last push: 2026-06-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-08. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

api api-client client hashicorp node node-vault nodejs secrets vault

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/node-vault.svg)](https://argusic.com/subject/node-vault)

Questions

Does node-vault run?: node-vault has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test node-vault?: On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for node-vault?: All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.