← Home

@midwayjs/koa

npm Repository Homepage

Midway Web Framework for KOA

15
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

czy88840616legendecasechosoarlellansinlxxyxstone-jinmariodu

Keywords

midwayIoCwebscenekoa

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Established midwayjs monorepo package; no script/dep changes vs prior version; dormancy consistent with monorepo release cadence. ai
dependencies unvetted-dep:@midwayjs/cookies AI (dependencies): First-party @midwayjs scoped package; expected dependency for this framework. ai
dependencies unvetted-dep:@types/qs AI (dependencies): Type-only dependency; stable for this framework package across versions. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'joi' is a false positive. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'zod' is a false positive. ai
phantom-deps phantom-dep:@types/qs AI (phantom-deps): @types/qs is a type-only dep used by TypeScript consumers; not directly imported at runtime. ai
phantom-deps phantom-dep:@types/koa AI (phantom-deps): @types/koa is a type-only dep; not directly imported at runtime, expected for a Koa framework wrapper. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'got' is a false positive. ai

Versions (showing 15 of 15)

Version Deps Published
4.1.0 8 / 5
4.0.3 8 / 5
4.0.2 8 / 5
4.0.1 8 / 5
4.0.0 8 / 5
3.20.24 9 / 4
3.20.23 9 / 4
3.20.22 9 / 4
3.20.19 9 / 4
3.20.16 9 / 4
3.20.15 9 / 4
3.20.13 9 / 4
3.20.12 9 / 3
3.20.11 9 / 3
3.20.5 9 / 3

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.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.

v4.0.2

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.

v4.0.1

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.

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.20.24

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.

v3.20.23

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.

v3.20.22

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.

v3.20.19

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.

v3.20.16

1 finding
LOW No provenance attestation provenance

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

v3.20.15

1 finding
LOW No provenance attestation provenance

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

v3.20.13

1 finding
LOW No provenance attestation provenance

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

v3.20.12

1 finding
LOW No provenance attestation provenance

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

v3.20.11

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.

v3.20.5

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.