@salesforce/code-analyzer-eslint-engine
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): ESLint engine package; typescript referenced in config files, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only framework package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint plugin referenced in config files; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint plugin referenced in config files; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:@lwc/eslint-plugin-lwc | AI (phantom-deps): LWC ESLint plugin referenced in config files; consistent with package purpose. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Referenced in ESLint config files; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Referenced in ESLint config files; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:@salesforce/eslint-plugin-lightning | AI (phantom-deps): Same-org ESLint plugin referenced in config files; consistent with package purpose. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.43.0 | 22 / 8 | |
| 0.42.0 | 22 / 8 | |
| 0.41.0 | 22 / 8 | |
| 0.40.2 | 22 / 8 | |
| 0.38.0 | 18 / 8 | |
| 0.37.1 | 18 / 8 | |
| 0.37.0 | 19 / 8 | |
| 0.36.0 | 18 / 8 | |
| 0.35.0 | 18 / 8 | |
| 0.34.0 | 18 / 8 | |
| 0.33.0 | 18 / 8 | |
| 0.32.0 | 18 / 8 | |
| 0.31.0 | 18 / 8 | |
| 0.30.0 | 18 / 9 | |
| 0.29.0 | 17 / 9 | |
| 0.28.0 | 17 / 9 | |
| 0.27.0 | 17 / 9 | |
| 0.26.2 | 17 / 9 | |
| 0.26.1 | 17 / 9 | |
| 0.26.0 | 17 / 9 |
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.