@itentialopensource/adapter-vmware_vsphere
This adapter integrates with system described as: vmware vsphere
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 pattern; preinstall runs setup.js for adapter scaffolding, stable across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads sibling adapter files by path — standard Itential adapter framework pattern, not arbitrary user input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility/troubleshooting scripts; consistent with Itential adapter framework across all versions. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in config/connectivity checks; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup utilities; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 0.9.4 | 15 / 6 | |
| 0.9.3 | 15 / 6 | |
| 0.9.2 | 15 / 6 | |
| 0.9.1 | 15 / 6 |
v1.0.2
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.