@leaflink/eslint-config
Opinionated linting configuration for LeafLink's front-end repositories.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): es-toolkit is a well-established lodash alternative; swap from lodash.has is benign. | ai | |
| dependencies | unvetted-dep:@vitest/eslint-plugin | AI (dependencies): @vitest/eslint-plugin is the official Vitest ESLint plugin; legitimate dependency for a linting config package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier.js is a shipped config file; prettier is a legitimate runtime dep for an eslint-config package. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): eslint-config-prettier is composed into the exported eslint config; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:@commitlint/cli | AI (phantom-deps): commitlint.js is a shipped config file; @commitlint/cli is a legitimate runtime dep. | ai | |
| phantom-deps | phantom-dep:@commitlint/config-conventional | AI (phantom-deps): Used in the shipped commitlint config; not a phantom dep. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 19 / 6 | |
| 5.2.0 | 19 / 6 | |
| 5.1.3 | 19 / 6 | |
| 5.1.0 | 19 / 6 | |
| 5.0.1 | 19 / 6 | |
| 4.4.2 | 19 / 5 | |
| 4.4.1 | 19 / 5 | |
| 3.0.0 | 19 / 6 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.