@maroonedsoftware/koa
Koa middleware, body parsing, and utilities for ServerKit
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher is confirmed by SLSA provenance attestation; consistent with org automation. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @maroonedsoftware/koa; name reflects koa framework wrapper, not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @maroonedsoftware/koa; name reflects koa framework wrapper, not a typosquat of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @maroonedsoftware/koa; name reflects koa framework wrapper, not a typosquat of 'zod'. | ai | |
| phantom-deps | phantom-dep:co-body | AI (phantom-deps): co-body is a declared runtime dep used in body parsing; phantom-dep heuristic fires because it's not directly imported at top level. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 15 / 11 | |
| 2.2.16 | 14 / 10 | |
| 2.2.15 | 14 / 10 | |
| 2.2.14 | 14 / 10 | |
| 2.2.13 | 14 / 10 | |
| 2.2.12 | 14 / 10 | |
| 2.2.11 | 14 / 10 | |
| 2.2.10 | 14 / 10 | |
| 2.2.9 | 14 / 10 | |
| 2.2.8 | 14 / 10 | |
| 2.2.7 | 14 / 10 | |
| 2.2.6 | 14 / 10 | |
| 2.2.5 | 14 / 10 | |
| 2.2.4 | 14 / 10 | |
| 2.2.3 | 14 / 10 | |
| 2.2.2 | 14 / 10 | |
| 2.2.1 | 14 / 10 | |
| 2.2.0 | 14 / 10 | |
| 2.1.21 | 13 / 10 | |
| 2.1.20 | 13 / 10 | |
| 2.1.19 | 13 / 10 | |
| 2.1.18 | 13 / 10 | |
| 2.1.17 | 13 / 10 | |
| 2.1.16 | 13 / 10 | |
| 2.1.15 | 13 / 10 | |
| 2.1.14 | 13 / 10 | |
| 2.1.13 | 13 / 10 | |
| 2.1.12 | 13 / 10 | |
| 2.1.11 | 13 / 10 | |
| 2.1.10 | 13 / 10 | |
| 2.1.9 | 13 / 10 | |
| 2.1.8 | 13 / 10 | |
| 2.1.7 | 13 / 10 | |
| 2.1.6 | 13 / 10 | |
| 2.1.5 | 13 / 10 | |
| 2.1.4 | 13 / 10 | |
| 2.1.3 | 13 / 10 | |
| 2.1.2 | 13 / 10 | |
| 2.1.1 | 13 / 10 | |
| 2.1.0 | 13 / 10 | |
| 2.0.0 | 13 / 10 | |
| 1.17.10 | 13 / 10 | |
| 1.17.9 | 13 / 10 | |
| 1.17.8 | 13 / 10 | |
| 1.17.7 | 13 / 10 | |
| 1.17.6 | 13 / 10 | |
| 1.17.5 | 13 / 10 | |
| 1.17.4 | 13 / 10 | |
| 1.17.3 | 13 / 10 | |
| 1.17.2 | 13 / 10 | |
| 1.17.1 | 13 / 10 | |
| 1.17.0 | 13 / 10 | |
| 1.16.6 | 13 / 10 | |
| 1.16.5 | 13 / 10 | |
| 1.16.4 | 13 / 10 | |
| 1.16.3 | 13 / 10 | |
| 1.16.2 | 13 / 10 | |
| 1.16.1 | 13 / 10 | |
| 1.16.0 | 13 / 10 | |
| 1.15.6 | 13 / 10 | |
| 1.15.5 | 13 / 10 | |
| 1.15.4 | 13 / 10 | |
| 1.15.3 | 13 / 10 | |
| 1.15.2 | 13 / 10 | |
| 1.15.1 | 13 / 10 | |
| 1.15.0 | 13 / 10 | |
| 1.14.1 | 13 / 10 | |
| 1.14.0 | 13 / 10 | |
| 1.13.5 | 13 / 10 | |
| 1.13.4 | 13 / 10 | |
| 1.13.3 | 13 / 10 | |
| 1.13.2 | 13 / 10 | |
| 1.13.1 | 13 / 10 | |
| 1.13.0 | 13 / 10 | |
| 1.12.1 | 13 / 10 | |
| 1.12.0 | 13 / 10 | |
| 1.11.0 | 13 / 10 | |
| 1.10.2 | 13 / 10 | |
| 1.10.1 | 13 / 10 | |
| 1.10.0 | 13 / 10 | |
| 1.9.0 | 13 / 10 | |
| 1.8.1 | 13 / 10 | |
| 1.8.0 | 13 / 10 | |
| 1.7.0 | 13 / 10 | |
| 1.6.2 | 13 / 10 | |
| 1.6.1 | 13 / 10 | |
| 1.6.0 | 13 / 10 | |
| 1.5.0 | 12 / 10 | |
| 1.4.0 | 12 / 10 | |
| 1.3.0 | 12 / 10 | |
| 1.2.1 | 12 / 10 | |
| 1.2.0 | 12 / 10 | |
| 1.1.1 | 7 / 8 | |
| 1.1.0 | 7 / 8 | |
| 1.0.0 | 6 / 7 |
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.