← Home

@itentialopensource/adapter-venafi

This adapter implements Api for Venafi as a Service

3
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 PlatformAutomationIntegrationAdapterSecurityVenafiPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Itential adapter pattern; preinstall runs utils/setup.js, consistent across all adapter versions. ai
semgrep semgrep:dynamic-require AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — static path, not truly dynamic/arbitrary. ai
semgrep semgrep:child-process-import AI (semgrep): Standard adapter tooling pattern for Itential adapters; execSync/spawnSync used for utility scripts. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Used in config/test files; stable false positive for this adapter package. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Used in utility scripts; stable false positive for this adapter package. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Used in test config; stable false positive for this adapter package. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6

v1.0.3

1 finding
LOW No provenance attestation provenance

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

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.

v1.0.0

1 finding
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.