← Home

@itentialopensource/adapter-vmware_virtual_infrastructure

This adapter integrates with system described as: Virtual Infrastructure.

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 PlatformAutomationIntegrationAdaptervmware_virtual_infrastructurePre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup hook; runs utils/setup.js for git hook configuration, consistent across all adapter versions. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for connectivity/health-check utilities; stable pattern across Itential adapter framework. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads sampleProperties.json via __dirname — path-anchored, not user-controlled; stable false positive for this package. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity utilities referenced via config/scripts, not direct import; stable false positive. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive CLI utilities; referenced in config files, stable false positive. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test runner plugin loaded via mocha config, not direct import; stable false positive. 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

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.