eslint-config-oclif
eslint config for oclif
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:eslint-config-xo-space | AI (dependencies): eslint-config-xo-space is a well-known XO style ESLint config; its use here is expected and stable across versions. | ai | |
| phantom-deps | phantom-dep:@eslint/eslintrc | AI (phantom-deps): ESLint config package; plugins loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-config-oclif | AI (phantom-deps): ESLint config package; referenced in config files, not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-config-xo-space | AI (phantom-deps): ESLint config package; referenced in config files, not directly imported. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): ESLint config package; plugins loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config package; parser referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config package; plugins loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config package; resolver referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@stylistic/eslint-plugin | AI (phantom-deps): ESLint config package; plugins loaded by convention, not direct import. | ai |
Versions (showing 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 6.0.62 | 17 / 3 | |
| 6.0.61 | 17 / 3 | |
| 6.0.60 | 17 / 3 | |
| 6.0.59 | 17 / 3 | |
| 6.0.58 | 17 / 3 | |
| 6.0.57 | 17 / 3 | |
| 6.0.56 | 17 / 3 | |
| 6.0.55 | 17 / 3 | |
| 6.0.54 | 17 / 3 | |
| 6.0.53 | 17 / 3 | |
| 6.0.52 | 17 / 3 | |
| 6.0.51 | 17 / 3 | |
| 6.0.50 | 17 / 3 |
v6.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.