← Home

@itentialopensource/adapter-salesforce_apex

npm Repository Homepage

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

9
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 PlatformAutomationIntegrationAdapterITSMTestingSalesforceApexPre-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 with 33 versions; no material changes in this release; publisher has strong approval track record. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require uses path.join(__dirname, ...) with static string — not user-controlled; stable false positive for this package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for adapter utility scripts (migration, healthcheck); standard Itential adapter pattern. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter pattern; preinstall runs utils/setup.js for hook setup, consistent across all adapter versions. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts; stable false positive for this adapter pattern. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param used in test scripts referenced via config; stable false positive. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/troubleshoot utility scripts referenced in config, not directly imported in main code. ai

Versions (showing 9 of 9)

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

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