connect
High performance middleware framework
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Connect v2.x bundles many middleware files by design; the large file count reflects the v2 batteries-included architecture, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to bundled middleware in connect v2.x vs the stripped-down v3.x baseline used for comparison; not indicative of injected payloads. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to lazily load connect's own bundled middleware from ./middleware/ directory — a stable, intentional design pattern for this package, not arbitrary code loading. | ai | |
| dependencies | unvetted-dep:basic-auth-connect | AI (dependencies): basic-auth-connect is a legitimate connect middleware dependency, pinned to 1.0.0, and has been part of connect's dependency tree for years. | ai |
Versions (showing 51 of 168)
| Version | Deps | Published |
|---|---|---|
| 3.7.0 | 4 / 4 | |
| 3.6.6 | 4 / 4 | |
| 3.6.5 | 4 / 4 | |
| 3.6.4 | 4 / 4 | |
| 3.6.3 | 4 / 3 | |
| 3.6.2 | 4 / 3 | |
| 3.6.1 | 4 / 3 | |
| 3.6.0 | 4 / 3 | |
| 3.5.1 | 4 / 3 | |
| 3.5.0 | 4 / 3 | |
| 3.4.1 | 4 / 3 | |
| 3.4.0 | 4 / 4 | |
| 3.3.5 | 4 / 4 | |
| 3.3.4 | 4 / 4 | |
| 3.3.3 | 4 / 4 | |
| 3.3.2 | 4 / 4 | |
| 3.3.1 | 4 / 4 | |
| 3.3.0 | 4 / 4 | |
| 3.2.0 | 4 / 4 | |
| 3.1.1 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.30.2 | 31 / 4 | |
| 2.30.1 | 31 / 4 | |
| 2.30.0 | 31 / 4 | |
| 2.29.2 | 31 / 4 | |
| 2.29.1 | 31 / 4 | |
| 2.29.0 | 31 / 4 | |
| 2.28.3 | 31 / 4 | |
| 2.28.2 | 31 / 4 | |
| 2.28.1 | 31 / 4 | |
| 2.28.0 | 31 / 4 | |
| 2.27.6 | 31 / 4 | |
| 2.27.5 | 31 / 4 | |
| 2.27.4 | 31 / 5 | |
| 2.27.3 | 31 / 5 | |
| 2.27.2 | 31 / 5 | |
| 2.27.1 | 31 / 5 | |
| 2.27.0 | 31 / 5 | |
| 2.26.6 | 29 / 5 | |
| 2.26.5 | 29 / 5 | |
| 2.26.4 | 29 / 5 | |
| 2.26.3 | 29 / 5 | |
| 2.26.2 | 29 / 5 | |
| 2.26.1 | 29 / 5 | |
| 2.26.0 | 29 / 5 | |
| 2.25.10 | 29 / 5 | |
| 2.25.9 | 29 / 5 | |
| 2.25.8 | 29 / 5 |
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.