@itentialopensource/adapter-openstack_neutron
This adapter integrates with system described as: Openstack Networking (Neutron) Service
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test/dev dependency used across all Itential adapter versions; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for standard adapter operations; stable pattern across Itential adapter framework. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads local sampleProperties.json via __dirname; not arbitrary module loading, stable pattern for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter preinstall pattern running local setup.js; consistent across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive utility scripts; phantom-dep heuristic false positive for this adapter. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test config files; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in config/connectivity scripts; phantom-dep heuristic false positive. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 15 / 6 | |
| 4.0.1 | 15 / 6 | |
| 4.0.0 | 15 / 6 | |
| 3.7.4 | 15 / 6 | |
| 3.7.3 | 15 / 6 | |
| 3.7.2 | 15 / 6 | |
| 3.7.0 | 15 / 6 | |
| 3.6.0 | 15 / 6 | |
| 3.5.1 | 15 / 6 | |
| 3.5.0 | 15 / 6 |
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.0.0
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.
v3.7.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.
v3.7.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.
v3.7.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.
v3.7.0
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.
v3.6.0
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.
v3.5.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.
v3.5.0
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.