@liberfi.io/eslint-config
Shared ESLint configuration for the Liberfi React SDK monorepo. Provides a single flat config that covers TypeScript, React, code style, and monorepo boundary enforcement, consumed at the root level so individual packages need no ESLint setup.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:eslint-config-eslint | AI (dependencies): Legitimate ESLint config package; stable dependency for this eslint-config package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-monorepo-cop | AI (dependencies): Legitimate ESLint plugin for monorepo enforcement; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): ESLint flat-config convention; loaded by config convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-config-turbo | AI (phantom-deps): Referenced in config files by convention, not direct import; stable false positive for ESLint config packages. | ai | |
| phantom-deps | phantom-dep:eslint-config-eslint | AI (phantom-deps): Referenced in config files by convention, not direct import; stable false positive for ESLint config packages. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.1.220 | 12 / 0 | |
| 0.1.219 | 12 / 0 | |
| 0.1.218 | 12 / 0 | |
| 0.1.217 | 12 / 0 | |
| 0.1.216 | 12 / 0 | |
| 0.1.215 | 12 / 0 | |
| 0.1.214 | 12 / 0 | |
| 0.1.213 | 12 / 0 | |
| 0.1.212 | 12 / 0 | |
| 0.1.211 | 12 / 0 | |
| 0.1.210 | 12 / 0 | |
| 0.1.209 | 12 / 0 | |
| 0.1.208 | 12 / 0 | |
| 0.1.207 | 12 / 0 | |
| 0.1.206 | 12 / 0 | |
| 0.1.205 | 12 / 0 | |
| 0.1.204 | 12 / 0 | |
| 0.1.203 | 12 / 0 | |
| 0.1.202 | 12 / 0 | |
| 0.1.201 | 12 / 0 | |
| 0.1.200 | 12 / 0 | |
| 0.1.199 | 12 / 0 | |
| 0.1.198 | 12 / 0 | |
| 0.1.197 | 12 / 0 | |
| 0.1.196 | 12 / 0 | |
| 0.1.195 | 12 / 0 | |
| 0.1.194 | 12 / 0 | |
| 0.1.193 | 12 / 0 | |
| 0.1.192 | 12 / 0 | |
| 0.1.191 | 12 / 0 | |
| 0.1.190 | 12 / 0 | |
| 0.1.189 | 12 / 0 | |
| 0.1.188 | 12 / 0 | |
| 0.1.187 | 12 / 0 | |
| 0.1.186 | 12 / 0 | |
| 0.1.185 | 12 / 0 | |
| 0.1.184 | 12 / 0 | |
| 0.1.183 | 12 / 0 | |
| 0.1.160 | 12 / 0 | |
| 0.1.79 | 12 / 0 | |
| 0.1.71 | 12 / 0 | |
| 0.1.6 | 12 / 0 |
v0.1.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.