@salesforce/mcp-provider-code-analyzer
(For Interal Use Only) Provides MCP Tools for Salesforce Code Analyzer to a MCP Server
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-admin is a Salesforce org account; addition alongside mass removal is consistent with internal consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal of individual contributors in favor of org account is standard Salesforce package governance. | ai | |
| dependencies | unvetted-dep:@salesforce/code-analyzer-eslint-engine | AI (dependencies): First-party Salesforce code-analyzer engine; consistent with the rest of the dependency set. | ai | |
| provenance | no-provenance | AI (provenance): Established Salesforce org publisher; absence of Sigstore provenance is not a risk signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Explicitly marked internal-use package; sparse README and no keywords are expected for internal tooling. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 10 / 10 | |
| 0.8.0 | 10 / 10 | |
| 0.7.1 | 10 / 10 | |
| 0.7.0 | 10 / 10 | |
| 0.6.0 | 10 / 10 | |
| 0.5.2 | 9 / 10 | |
| 0.5.1 | 9 / 10 | |
| 0.5.0 | 9 / 10 | |
| 0.4.0 | 9 / 10 | |
| 0.3.1 | 9 / 10 | |
| 0.3.0 | 9 / 10 | |
| 0.2.2 | 9 / 10 | |
| 0.2.0 | 9 / 9 | |
| 0.1.0 | 9 / 9 | |
| 0.0.2 | 9 / 9 | |
| 0.0.1 | 9 / 9 |
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.