@itentialopensource/adapter-salesforce_rest
This adapter integrates with system described as: Salesforce REST.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test-only helper used across Itential adapter versions; stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Itential adapter pattern: requires local adapterBase.js via path.join(__dirname,...); not arbitrary user input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in adapterBase.js for connectivity/healthcheck utilities; standard across Itential adapter ecosystem. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework standard setup hook; runs local node script, not a remote fetch. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive utility scripts; referenced in config files as expected. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test scripts; referenced in config files as expected. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity/healthcheck scripts referenced in package.json scripts; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.6.0 | 15 / 6 | |
| 0.4.1 | 15 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.