← Home

@itentialopensource/adapter-bluecat_ipam

npm Repository Homepage

This adapter integrates with system described as: BlueCat IPAM

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:mocha-param AI (dependencies): mocha-param is a test-runner helper used in Itential adapter framework; stable pattern across their adapter family. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity tooling scripts, not directly imported in main code. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in CLI utility scripts, not main adapter code. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param used in test files via mocha config, not directly imported in source. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter framework operations; stable pattern across Itential adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves local config/properties files via __dirname; not arbitrary user input. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script pattern; consistent across the adapter family. ai

Versions (showing 4 of 4)

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

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.