← Home

@itentialopensource/adapter-salt

npm Repository Homepage

This adapter integrates with system described as: Salt.

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 PlatformAutomationIntegrationAdapterDevOpsNetOpsSaltPre-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 pattern; stable across all versions of this package family. ai
semgrep semgrep:dynamic-require AI (semgrep): Adapter framework loads modules by path construction; benign pattern consistent across Itential adapters. ai
semgrep semgrep:child-process-import AI (semgrep): HTTP adapter base class uses execSync/spawnSync for connectivity/healthcheck utilities; documented and expected. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in adapter connectivity utilities via config; stable false positive for this package. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in setup/migration utilities referenced in config; stable false positive. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param used in test files referenced via config; 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.3 15 / 6
0.9.2 15 / 6
0.9.1 15 / 6

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.

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

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