← Home

@itentialopensource/adapter-apic

npm Repository Homepage

Cisco Application Policy Infrastructure Controller (Cisco APIC) is the unifying point of automation and management for the Application Centric Infrastructure (ACI) fabric.

7
Versions
SEE LICENSE IN LICENSE
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 PlatformAutomationIntegrationAdapterSecurityCisco APICCisco ACIPre-Release

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 org package; inactivity gap consistent with product release cadence, no suspicious changes. ai
semgrep semgrep:dynamic-require AI (semgrep): Adapter framework loads modules via path.join(__dirname, ...) — safe local path construction, not user-controlled input. ai
semgrep semgrep:child-process-import AI (semgrep): Adapter base uses execSync/spawnSync for connectivity/healthcheck utilities; consistent with documented adapter functionality. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script pattern; runs local node utility, not remote code. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts is used in interactive setup utilities; phantom-dep heuristic false positive for this adapter pattern. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param referenced in test config files; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is a declared runtime dependency used in config/connectivity checks; phantom-dep heuristic false positive. ai

Versions (showing 7 of 7)

Version Deps Published
1.0.2 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6
0.16.4 15 / 6
0.16.2 15 / 6
0.16.0 15 / 6
0.13.0 15 / 6

v1.0.2

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

v0.16.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.

v0.16.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.13.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.