← Home

@itentialopensource/adapter-infoblox

npm Repository Homepage

Itential Infoblox Adapter

6
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

Itential PlatformItentialAutomationIntegrationAdapterInventoryIPAMDNSDHCPDDIInfobloxReleased

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-lived Itential adapter with 70 versions; publisher has 454 approved packages and no material diff from prior version. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter lifecycle management; stable pattern across Itential adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic requires in adapterBase.js load config/property files by path; standard Itential adapter framework pattern. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework standard setup script; consistent across all adapter-* packages in this org. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive setup/migration utilities; not directly imported in main adapter code. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test utility referenced via mocha config rather than direct import. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in adapter connectivity utilities; referenced in config/scripts rather than direct import. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.2 15 / 6
2.0.1 15 / 6
2.0.0 15 / 6
1.20.3 15 / 6
1.20.0 15 / 6
1.19.2 15 / 6

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.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.

v2.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.

v1.20.3

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.20.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.

v1.19.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.