@salesforce/mcp
MCP Server for interacting with Salesforce instances
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @salesforce/mcp package; no meaningful similarity to 'yup' beyond edit distance. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Used in guessCI.js to detect CI environment by key prefix — standard config-detection pattern, not exfiltration. | ai | |
| phantom-deps | phantom-dep:@salesforce/kit | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/agents | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/ts-types | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/apex-node | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/source-tracking | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/source-deploy-retrieve | AI (phantom-deps): Same-org Salesforce dep; likely used transitively or via re-export pattern. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.30.10 | 20 / 19 | |
| 0.30.9 | 20 / 19 | |
| 0.30.6 | 20 / 19 | |
| 0.20.1 | 17 / 10 | |
| 0.20.0 | 17 / 10 | |
| 0.19.1 | 14 / 10 | |
| 0.19.0 | 14 / 10 | |
| 0.15.4 | 13 / 10 | |
| 0.15.3 | 13 / 10 | |
| 0.15.2 | 13 / 10 | |
| 0.15.1 | 13 / 10 | |
| 0.15.0 | 13 / 10 | |
| 0.14.3 | 13 / 10 | |
| 0.14.2 | 13 / 10 | |
| 0.14.1 | 13 / 10 | |
| 0.14.0 | 13 / 10 | |
| 0.13.2 | 13 / 10 | |
| 0.13.1 | 13 / 10 | |
| 0.13.0 | 13 / 10 | |
| 0.12.0 | 12 / 10 | |
| 0.11.4 | 12 / 10 | |
| 0.11.3 | 12 / 10 | |
| 0.11.2 | 12 / 10 | |
| 0.11.1 | 12 / 10 | |
| 0.11.0 | 12 / 10 | |
| 0.10.2 | 12 / 10 | |
| 0.10.1 | 12 / 10 | |
| 0.10.0 | 12 / 10 | |
| 0.9.1 | 12 / 10 | |
| 0.9.0 | 12 / 10 | |
| 0.8.2 | 12 / 10 | |
| 0.8.1 | 12 / 10 | |
| 0.7.0 | 12 / 10 | |
| 0.6.3 | 11 / 10 | |
| 0.6.2 | 11 / 10 | |
| 0.6.1 | 11 / 10 | |
| 0.6.0 | 11 / 10 | |
| 0.5.0 | 10 / 10 | |
| 0.4.3 | 10 / 10 | |
| 0.4.2 | 10 / 10 | |
| 0.4.1 | 10 / 10 | |
| 0.4.0 | 10 / 10 | |
| 0.3.0 | 9 / 10 | |
| 0.2.8 | 8 / 9 | |
| 0.2.7 | 8 / 9 | |
| 0.2.6 | 8 / 9 | |
| 0.2.5 | 8 / 9 |
v0.30.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: salesforce-releases.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: salesforce-releases.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.