@itentialopensource/adapter-salesforce_tooling
This adapter integrates with system described as: Salesforce Tooling.
2
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 PlatformAutomationIntegrationAdapterITSMTestingSalesforceToolingPre-Release
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup utility; consistent pattern across all adapter versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — static path, not user-controlled; standard adapter pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility scripts (setup, migration, healthcheck); consistent with Itential adapter framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is declared in dependencies and used in adapter connectivity utilities; stable false positive. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup/migration scripts; referenced in config files as expected. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test files; phantom-dep heuristic misses test file imports. | ai |
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.