← Home

@itentialopensource/adapter-salesforce_metadata

This adapter integrates with system described as: Salesforce Metadata API.

3
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 PlatformAutomationIntegrationAdapterITSMTestingSalesforceMetadataPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Established Itential adapter org with verified publisher track record; dormancy consistent with infrequent maintenance releases. ai
semgrep semgrep:dynamic-require AI (semgrep): Requires adapterBase.js by __dirname-relative path; not user-controlled input. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for adapter utility/healthcheck operations; consistent with Itential adapter framework. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter pattern; setup.js runs adapter initialization, not arbitrary remote code. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Used in adapter setup utilities; stable false positive for this package. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Used in test config files; stable false positive for this package. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Used in adapter config/connectivity checks; stable false positive for this package. ai

Versions (showing 3 of 3)

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