@sailshq/connect
High performance middleware framework
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
sgress454
Keywords
frameworkwebmiddlewareconnectrack
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is over a bounded local ./middleware/ directory by filename — a well-known pattern in the original connect framework, not arbitrary user-controlled input. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by years; no provenance is expected and not a risk signal for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.30.3 | 31 / 4 |
v2.30.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.