← Home

@itentialopensource/adapter-bluecat

npm Repository Homepage

This adapter integrates with system described as: BlueCat ProteusAPI.

5
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 PlatformAutomationIntegrationAdapterInventoryIPAMDNSDHCPBluecatPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework uses node utils/setup.js preinstall consistently across all adapters; not arbitrary code execution. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in Itential adapter base is a stable framework pattern for loading adapter components, not arbitrary user input. ai
semgrep semgrep:child-process-import AI (semgrep): child_process usage in adapterBase.js is part of Itential's adapter-utils framework; stable across versions. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in config/connectivity utilities, not directly imported in main code; stable false positive for this adapter. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts, not main adapter code; stable false positive. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param referenced in test config files; stable false positive for this adapter. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.3 15 / 8
1.0.2 15 / 8
1.0.1 15 / 8
0.12.5 15 / 8
0.12.0 15 / 8

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

v0.12.5

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