@zthun/janitor-eslint-config
A shared configuration for eslint for @zthun scoped projects.
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 | dormant-publish | AI (publish-pattern): Publisher has 42 approved packages; dormancy aligns with a major version refactor, not account takeover. | ai | |
| dependencies | unvetted-dep:@vitest/eslint-plugin | AI (dependencies): @vitest/eslint-plugin is the official vitest ESLint plugin; legitimate dependency for this eslint-config package. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): eslint-config-prettier is a declared runtime dep used via ESLint config extension, not a direct JS import — phantom-dep false positive for config packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 20.0.7 | 17 / 5 | |
| 20.0.6 | 17 / 5 | |
| 20.0.5 | 17 / 5 | |
| 20.0.4 | 17 / 5 | |
| 20.0.3 | 17 / 5 | |
| 20.0.2 | 17 / 5 | |
| 20.0.1 | 17 / 5 | |
| 20.0.0 | 17 / 5 | |
| 19.5.6 | 7 / 5 | |
| 19.5.4 | 7 / 5 | |
| 19.5.3 | 7 / 5 | |
| 19.5.2 | 7 / 5 | |
| 19.5.1 | 7 / 5 | |
| 19.5.0 | 7 / 5 | |
| 19.4.3 | 7 / 5 |
v20.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.