@sqb/builder
Extensible multi-dialect SQL query builder written with TypeScript
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:fast-tokenizer | AI (dependencies): Panates org package; stable dependency across many versions of @sqb/builder. | ai | |
| dependencies | unvetted-dep:putil-flattentext | AI (dependencies): Panates org utility package; consistent with this package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:putil-isplainobject | AI (dependencies): Panates org utility package; consistent with this package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:putil-merge | AI (dependencies): Panates org utility package; consistent with this package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:putil-varhelpers | AI (dependencies): Panates org utility package; consistent with this package's established dependency pattern. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is a declared runtime dep used transitively; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.0.4 | 7 / 0 | |
| 5.0.3 | 7 / 0 | |
| 5.0.2 | 7 / 0 | |
| 5.0.1 | 7 / 0 | |
| 5.0.0 | 7 / 0 | |
| 4.26.1 | 7 / 0 | |
| 4.26.0 | 6 / 0 | |
| 4.25.0 | 6 / 0 | |
| 4.24.1 | 6 / 0 | |
| 4.23.3 | 6 / 0 | |
| 4.23.1 | 6 / 0 | |
| 4.23.0 | 6 / 0 | |
| 4.22.0 | 6 / 0 | |
| 4.21.1 | 6 / 0 | |
| 4.21.0 | 6 / 0 | |
| 4.20.7 | 6 / 0 | |
| 4.20.6 | 6 / 0 | |
| 4.20.5 | 6 / 0 | |
| 4.20.4 | 6 / 0 | |
| 4.20.3 | 6 / 0 |
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
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.
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.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.