@ts-safeql/eslint-plugin
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent with CI/CD automation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish with valid provenance; not indicative of takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is a stable pattern, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 97 versions; no provenance is consistent across all prior releases. | ai | |
| dependencies | unvetted-dep:@ts-safeql/plugin-utils | AI (dependencies): Same-monorepo sibling package; expected dependency for this eslint-plugin. | ai | |
| dependencies | unvetted-dep:@ts-safeql/connection-manager | AI (dependencies): Same-monorepo sibling package; expected dependency for this eslint-plugin. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a declared runtime dependency used as a script runner; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:quansync | AI (phantom-deps): quansync is a declared runtime dependency; phantom-dep is a false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 10 / 16 | |
| 5.1.2 | 10 / 15 | |
| 5.1.1 | 10 / 15 | |
| 5.1.0 | 10 / 15 | |
| 5.0.0 | 11 / 13 | |
| 4.2.0 | 9 / 13 | |
| 4.1.1 | 9 / 13 | |
| 4.1.0 | 9 / 13 | |
| 4.0.9 | 9 / 13 | |
| 4.0.8 | 9 / 13 | |
| 4.0.7 | 9 / 13 | |
| 4.0.6 | 9 / 13 | |
| 4.0.5 | 10 / 13 | |
| 4.0.4 | 10 / 13 | |
| 4.0.3 | 10 / 13 |
v5.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.