@salesforce/code-analyzer-eslint8-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:@eslint/js | AI (phantom-deps): ESLint plugin loaded by convention in config files, not direct import; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Referenced in config files; standard peer-dep pattern for TypeScript ESLint engine. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel parser loaded by convention; expected for ESLint engine wrapper. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:typescript-eslint | AI (phantom-deps): Referenced in config files; standard pattern for this ESLint engine. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint plugin loaded via config; not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/eslint-parser | AI (phantom-deps): Parser loaded by convention; expected for Babel-based ESLint config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint plugin loaded via config; not directly imported. | ai | |
| phantom-deps | phantom-dep:@lwc/eslint-plugin-lwc | AI (phantom-deps): LWC ESLint plugin loaded via config; expected for Salesforce LWC engine. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Parser referenced in config files; standard pattern. | ai | |
| phantom-deps | phantom-dep:@lwc/eslint-plugin-lwc-platform | AI (phantom-deps): LWC platform plugin loaded via config; expected for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): TypeScript ESLint plugin loaded via config; standard pattern. | ai | |
| phantom-deps | phantom-dep:@salesforce/eslint-plugin-lightning | AI (phantom-deps): Same-org Salesforce package loaded via config; expected dependency pattern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 16 / 8 | |
| 0.14.0 | 16 / 8 | |
| 0.13.0 | 16 / 8 | |
| 0.12.0 | 16 / 8 | |
| 0.11.0 | 16 / 8 | |
| 0.10.0 | 16 / 8 | |
| 0.9.0 | 16 / 8 | |
| 0.8.0 | 16 / 8 | |
| 0.7.0 | 16 / 8 | |
| 0.6.0 | 16 / 8 | |
| 0.5.0 | 16 / 8 | |
| 0.4.0 | 16 / 8 | |
| 0.3.0 | 16 / 8 | |
| 0.2.0 | 17 / 7 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.