← Home

@itentialopensource/adapter-infoblox_threat_defense

This adapter integrates with system described as: Infoblox Threat Defense.

4
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 PlatformAutomationIntegrationAdapterinfoblox_threat_defensePre-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 script; runs local utils/setup.js for git hooks, consistent across all adapter versions. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves local files via path.join(__dirname, ...) — not user-controlled input; stable adapter framework pattern. ai
semgrep semgrep:child-process-import AI (semgrep): execSync/spawnSync used in adapterBase.js for adapter framework operations; standard Itential adapter pattern. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter package. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter package. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter package. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6
0.5.4 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.

v0.5.4

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.