@ts-safeql/generate
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 CI publishing is confirmed by SLSA provenance attestation; consistent with the ts-safeql org's release pipeline. | ai | |
| dependencies | unvetted-dep:@ts-safeql/sql-ast | AI (dependencies): Same-org monorepo sibling package; consistently co-released with this package. | ai | |
| dependencies | unvetted-dep:@ts-safeql/test-utils | AI (dependencies): Same-org monorepo sibling package; stable pattern across releases. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 28 approved packages and 0 rejections; no material changes from prior version; dormancy alone is insufficient signal here. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating widespread provenance adoption; no other risk signals present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with empty description field; not indicative of malicious intent for this established project. | ai | |
| phantom-deps | phantom-dep:@ts-safeql/test-utils | AI (phantom-deps): Same-org monorepo test utility; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:pg-connection-string | AI (phantom-deps): pg-connection-string is a runtime dep used in config/connection handling; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 3 / 13 | |
| 5.1.2 | 3 / 13 | |
| 5.1.1 | 3 / 13 | |
| 5.1.0 | 3 / 13 | |
| 5.0.0 | 6 / 9 | |
| 4.2.0 | 6 / 9 | |
| 4.1.1 | 6 / 9 | |
| 4.1.0 | 6 / 9 | |
| 4.0.9 | 6 / 9 | |
| 4.0.8 | 6 / 9 | |
| 4.0.7 | 6 / 9 | |
| 4.0.6 | 6 / 9 | |
| 4.0.5 | 6 / 9 | |
| 4.0.4 | 6 / 9 | |
| 4.0.3 | 6 / 9 |
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.