@sqb/connect
Multi-dialect database connection framework 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for TS packages. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Referenced in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:putil-merge | AI (phantom-deps): Author-owned utility; referenced in config files, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@jsopen/objects | AI (phantom-deps): Author-owned utility; referenced in config files, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:putil-promisify | AI (phantom-deps): Author-owned utility; referenced in config files, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:putil-isplainobject | AI (phantom-deps): Author-owned utility; referenced in config files, heuristic false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.0.4 | 14 / 0 | |
| 5.0.3 | 14 / 0 | |
| 5.0.2 | 14 / 0 | |
| 5.0.1 | 14 / 0 | |
| 5.0.0 | 14 / 0 | |
| 4.26.1 | 14 / 0 | |
| 4.26.0 | 14 / 0 | |
| 4.25.0 | 14 / 0 | |
| 4.24.1 | 14 / 0 | |
| 4.23.3 | 14 / 0 | |
| 4.23.1 | 14 / 0 | |
| 4.23.0 | 14 / 0 | |
| 4.22.0 | 14 / 0 | |
| 4.21.1 | 14 / 0 | |
| 4.21.0 | 14 / 0 | |
| 4.20.7 | 14 / 0 | |
| 4.20.6 | 14 / 0 | |
| 4.20.5 | 14 / 0 | |
| 4.20.4 | 14 / 0 | |
| 4.20.3 | 13 / 0 |
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.6
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.20.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.20.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.20.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.