@slango.configs/eslint
Slango eslint configs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-config-next | AI (phantom-deps): ESLint config packages reference configs in files, not code imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages reference configs in files, not code imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages reference configs in files, not code imports; stable pattern. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 1.0.15 | 17 / 0 | |
| 1.0.14 | 17 / 0 | |
| 1.0.13 | 17 / 0 | |
| 1.0.12 | 17 / 0 | |
| 1.0.11 | 17 / 0 | |
| 1.0.10 | 17 / 0 | |
| 1.0.9 | 17 / 0 | |
| 1.0.8 | 17 / 0 | |
| 1.0.7 | 17 / 0 | |
| 1.0.6 | 17 / 0 | |
| 1.0.5 | 17 / 0 | |
| 1.0.4 | 17 / 0 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.