← Home

@itentialopensource/adapter-cloudify

This adapter integrates with system described as: cloudify.

7
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 PlatformAutomationIntegrationAdapterControllerOrchestratorCloudifyPre-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 gaps are normal for niche integration adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — static path, not truly dynamic; stable false positive for this package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapter base for system interaction; standard pattern in Itential adapter framework. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter framework setup script; consistent across all adapter-* packages in this org. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Used in setup/utility scripts, not main adapter code; stable false positive. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Test utility referenced in test configs; stable false positive for this package. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Used in config/connectivity utilities, not directly imported in main code; stable 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.9.4 15 / 6
0.9.2 15 / 6
0.7.1 15 / 6
0.7.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.9.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.9.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.7.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.7.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.