@midwayjs/koa MIT 32 versions

@midwayjs/koa

npm Repository Homepage

Midway Web Framework for KOA

32

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

czy88840616legendecasechosoarlellansinlxxyxstone-jinmariodu

Keywords

midwayIoCwebscenekoa

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/05/09
dependencies	unvetted-dep:@midwayjs/cookies	AI (dependencies): First-party @midwayjs scoped package; expected dependency for this framework.	ai	2026/04/28
dependencies	unvetted-dep:@types/qs	AI (dependencies): Type-only dependency; stable for this framework package across versions.	ai	2026/04/28
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'joi' is a false positive.	ai	2026/04/28
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'zod' is a false positive.	ai	2026/04/28
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	2026/04/28
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	2026/04/28
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped package @midwayjs/koa; Levenshtein match to 'got' is a false positive.	ai	2026/04/28

Versions (showing 32 of 132)

Version	Deps	Published
3.4.4	6 / 6	2022-07-25
3.4.3	6 / 6	2022-07-21
3.4.1	6 / 6	2022-07-20
3.4.0	6 / 6	2022-07-20
3.3.7	6 / 6	2022-06-18
3.3.6	6 / 6	2022-05-11
3.3.5	6 / 6	2022-04-27
3.3.4	6 / 6	2022-04-21
3.3.2	6 / 6	2022-04-13
3.3.1	6 / 6	2022-04-11
3.3.0	6 / 6	2022-04-07
3.2.2	6 / 6	2022-03-30
3.2.1	6 / 6	2022-03-27
3.2.0	6 / 6	2022-03-25
3.1.6	6 / 6	2022-03-21
3.1.5	6 / 6	2022-03-18
3.1.2	6 / 6	2022-03-15
3.1.1	6 / 6	2022-03-09
3.1.0	6 / 6	2022-03-07
3.0.13	6 / 6	2022-03-01
3.0.11	6 / 6	2022-02-25
3.0.10	6 / 6	2022-02-24
3.0.9	6 / 6	2022-02-21
3.0.8	6 / 6	2022-02-19
3.0.7	6 / 6	2022-02-17
3.0.6	6 / 6	2022-02-13
3.0.5	6 / 6	2022-02-10
3.0.4	6 / 6	2022-02-09
3.0.3	6 / 6	2022-01-28
3.0.2	6 / 6	2022-01-24
3.0.1	6 / 6	2022-01-24
3.0.0	6 / 6	2022-01-20

v3.4.4

1 finding

LOW No provenance attestation provenance

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

v3.4.3

1 finding

LOW No provenance attestation provenance

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

v3.4.1

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.7

1 finding

LOW No provenance attestation provenance

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

v3.3.6

1 finding

LOW No provenance attestation provenance

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

v3.3.5

1 finding

LOW No provenance attestation provenance

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

v3.3.4

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.13

1 finding

LOW No provenance attestation provenance

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

v3.0.11

1 finding

LOW No provenance attestation provenance

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

v3.0.10

1 finding

LOW No provenance attestation provenance

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

v3.0.9

1 finding

LOW No provenance attestation provenance

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

v3.0.8

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.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.

v3.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.