@salesforce/plugin-code-analyzer
Salesforce Code Analyzer is a unified tool to help Salesforce developers analyze their source code for security vulnerabilities, performance issues, best practices, and more.
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:@salesforce/code-analyzer-eslint-engine | AI (dependencies): Same-org @salesforce scoped dep from a known Salesforce monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@salesforce/code-analyzer-sfge-engine | AI (dependencies): Same-org @salesforce scoped dep from a known Salesforce monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@salesforce/code-analyzer-flow-engine | AI (dependencies): Same-org @salesforce scoped dep from a known Salesforce monorepo; stable pattern across versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal Salesforce team rotation; publisher org (salesforce-releases) is well-established with strong approval history. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce-releases publisher with strong track record; no-provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Standard TypeScript runtime helper; declared as convention for SF CLI plugins. | ai | |
| phantom-deps | phantom-dep:@salesforce/ts-types | AI (phantom-deps): Same-org utility; used transitively by SF CLI core, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/js-yaml | AI (phantom-deps): Type-only package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package; framework-scoped, not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Referenced in config files only; standard for SF CLI plugin toolchain. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.13.0 | 20 / 15 | |
| 5.12.0 | 20 / 15 | |
| 5.11.1 | 20 / 15 | |
| 5.11.0 | 20 / 15 | |
| 5.10.2 | 20 / 15 | |
| 5.10.1 | 20 / 15 | |
| 5.10.0 | 20 / 15 | |
| 5.9.0 | 20 / 15 | |
| 5.8.0 | 20 / 15 | |
| 5.7.1 | 20 / 15 | |
| 5.7.0 | 20 / 15 | |
| 5.6.1 | 20 / 15 | |
| 5.6.0 | 20 / 15 | |
| 5.5.0 | 19 / 17 | |
| 5.4.0 | 19 / 16 | |
| 5.3.0 | 19 / 16 | |
| 5.2.2 | 19 / 16 | |
| 5.2.1 | 19 / 16 | |
| 5.2.0 | 19 / 16 | |
| 5.1.0 | 19 / 16 | |
| 5.0.0 | 19 / 16 |
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.