← Home

koa-connect

npm Repository Homepage

Use Connect/Express middleware in Koa

5
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

lourdvkurchatkin

Keywords

koaconnectexpressmiddleware

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition to lourd (listed contributor) in 2017; lourd has strong track record (19 approved, 0 rejected). ai
maintainer-change maintainer-added AI (maintainer-change): lourd added as maintainer in 2017; listed as contributor in package.json, long npm history. ai
source-diff source-size-tripled AI (source-diff): 1KB to 8KB is trivial in absolute terms; consistent with v2 rewrite adding tests. ai

Versions (showing 5 of 5)

Version Deps Published
2.1.1 0 / 14
2.1.0 0 / 14
2.0.1 0 / 3
2.0.0 0 / 3
1.0.0 1 / 1

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
HIGH Publisher changed: vkurchatkin → lourd (on 2017-01-12) provenance

This version was published by a different npm account than previous versions on 2017-01-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

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.