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 51 of 113)
| Version | Deps | Published |
|---|---|---|
| 6.0.166 | 17 / 3 | |
| 6.0.165 | 17 / 3 | |
| 6.0.164 | 17 / 3 | |
| 6.0.163 | 17 / 3 | |
| 6.0.162 | 17 / 3 | |
| 6.0.161 | 17 / 3 | |
| 6.0.160 | 17 / 3 | |
| 6.0.159 | 17 / 3 | |
| 6.0.158 | 17 / 3 | |
| 6.0.157 | 17 / 3 | |
| 6.0.156 | 17 / 3 | |
| 6.0.155 | 17 / 3 | |
| 6.0.154 | 17 / 3 | |
| 6.0.153 | 17 / 3 | |
| 6.0.152 | 17 / 3 | |
| 6.0.151 | 17 / 3 | |
| 6.0.150 | 17 / 3 | |
| 6.0.149 | 17 / 3 | |
| 6.0.148 | 17 / 3 | |
| 6.0.147 | 17 / 3 | |
| 6.0.146 | 17 / 3 | |
| 6.0.145 | 17 / 3 | |
| 6.0.144 | 17 / 3 | |
| 6.0.143 | 17 / 3 | |
| 6.0.142 | 17 / 3 | |
| 6.0.141 | 17 / 3 | |
| 6.0.140 | 17 / 3 | |
| 6.0.139 | 17 / 3 | |
| 6.0.138 | 17 / 3 | |
| 6.0.137 | 17 / 3 | |
| 6.0.136 | 17 / 3 | |
| 6.0.135 | 17 / 3 | |
| 6.0.134 | 17 / 3 | |
| 6.0.133 | 17 / 3 | |
| 6.0.132 | 17 / 3 | |
| 6.0.131 | 17 / 3 | |
| 6.0.130 | 17 / 3 | |
| 6.0.129 | 17 / 3 | |
| 6.0.128 | 17 / 3 | |
| 6.0.127 | 17 / 3 | |
| 6.0.126 | 17 / 3 | |
| 6.0.125 | 17 / 3 | |
| 6.0.124 | 17 / 3 | |
| 6.0.123 | 17 / 3 | |
| 6.0.122 | 17 / 3 | |
| 6.0.121 | 17 / 3 | |
| 6.0.120 | 17 / 3 | |
| 6.0.119 | 17 / 3 | |
| 6.0.118 | 17 / 3 | |
| 6.0.117 | 17 / 3 | |
| 6.0.116 | 17 / 3 |
v6.0.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.