@voicenter-team/eslint-config-ts
Shared eslint config
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are within the same VoicenterTeam org; consistent with internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removals paired with org-internal additions; no evidence of hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 4 new deps are canonical ESLint v9/v10 ecosystem packages; expected for a major version bump. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.0.25 | 0 / 4 | |
| 1.0.24 | 0 / 4 | |
| 1.0.23 | 0 / 4 | |
| 1.0.22 | 0 / 4 | |
| 1.0.21 | 0 / 4 | |
| 1.0.14 | 0 / 4 |
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.