@itentialopensource/adapter-hashicorp_vault
This adapter integrates with system described as: hashicorp_vault.
2
Versions
Apache-2.0
License
Yes
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
jared.obrienjohnpolanskyzack.strulovitchitential-ciandyknaebelishitaprakash
Keywords
ItentialItential PlatformAutomationIntegrationAdapterITSMTestingHashiCorpVaultPre-Release
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework uses setup.js preinstall for hook registration; stable pattern across all adapter versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage in adapterBase.js is part of Itential's standard adapter framework; not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in adapterBase.js loads local config files by path; stable framework pattern, not arbitrary code loading. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity utilities; referenced in config/scripts rather than direct imports. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive utility scripts; stable false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test files via mocha config; not directly imported in source. | ai |
v1.0.2
2 findings
HIGH
Package has 'preinstall' script
install-scripts
Script: node utils/setup.js
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.
v1.0.1
2 findings
HIGH
Package has 'preinstall' script
install-scripts
Script: node utils/setup.js
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.