@types/koa
TypeScript definitions for koa
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/accepts | AI (phantom-deps): @types/* packages are resolved by TypeScript's type system, not via direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/keygrip | AI (phantom-deps): @types/* packages are resolved by TypeScript's type system, not via direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/http-assert | AI (phantom-deps): @types/* packages are resolved by TypeScript's type system, not via direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/koa-compose | AI (phantom-deps): @types/* packages are resolved by TypeScript's type system, not via direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/cookies | AI (phantom-deps): @types/* packages conventionally declare type deps without direct imports; this is expected behavior for DefinitelyTyped packages. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @types/koa is the official DefinitelyTyped package for Koa; string similarity to 'got' is purely coincidental and not a typosquat risk. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @types/koa is the official DefinitelyTyped package for Koa; string similarity to 'joi' is purely coincidental and not a typosquat risk. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @types/koa is the official DefinitelyTyped package for Koa; string similarity to 'zod' is purely coincidental and not a typosquat risk. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a standard type-level dependency for DefinitelyTyped packages; not directly imported by convention. Stable false positive. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size reduction in a @types package reflects type definition refactoring, not malicious stubbing. Publisher track record and DefinitelyTyped repo confirm legitimacy. | ai | |
| email-domain | unclaimed-email:https://github.com/davidcai1993 | AI (email-domain): The 'email' field is a GitHub profile URL, not an email address. The analyzer is misinterpreting a URL as an email domain — stable false positive for this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 8 / 0 | |
| 3.0.2 | 8 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 | |
| 2.15.2 | 8 / 0 | |
| 2.15.1 | 8 / 0 | |
| 2.15.0 | 8 / 0 | |
| 2.14.0 | 8 / 0 | |
| 2.13.12 | 8 / 0 | |
| 2.13.11 | 8 / 0 | |
| 2.13.10 | 8 / 0 | |
| 2.13.9 | 8 / 0 | |
| 2.13.8 | 8 / 0 | |
| 2.13.7 | 8 / 0 | |
| 2.13.6 | 8 / 0 | |
| 2.13.5 | 8 / 0 | |
| 2.13.4 | 8 / 0 | |
| 2.13.3 | 8 / 0 | |
| 2.13.2 | 8 / 0 | |
| 2.13.1 | 8 / 0 | |
| 2.13.0 | 8 / 0 | |
| 2.11.8 | 8 / 0 | |
| 2.11.7 | 8 / 0 | |
| 2.11.6 | 8 / 0 | |
| 2.11.5 | 8 / 0 | |
| 2.11.4 | 8 / 0 | |
| 2.11.3 | 7 / 0 | |
| 2.11.2 | 6 / 0 | |
| 2.11.1 | 6 / 0 | |
| 2.11.0 | 6 / 0 | |
| 2.0.52 | 6 / 0 | |
| 2.0.51 | 6 / 0 | |
| 2.0.50 | 6 / 0 | |
| 2.0.49 | 6 / 0 | |
| 2.0.48 | 6 / 0 | |
| 2.0.47 | 6 / 0 | |
| 2.0.46 | 7 / 0 | |
| 2.0.45 | 7 / 0 | |
| 2.0.44 | 7 / 0 | |
| 2.0.43 | 7 / 0 | |
| 2.0.42 | 7 / 0 | |
| 2.0.41 | 6 / 0 | |
| 2.0.40 | 6 / 0 | |
| 2.0.39 | 6 / 0 | |
| 2.0.38 | 6 / 0 | |
| 2.0.37 | 2 / 0 | |
| 2.0.36 | 2 / 0 | |
| 2.0.35 | 2 / 0 | |
| 2.0.34 | 2 / 0 | |
| 2.0.33 | 2 / 0 | |
| 2.0.32 | 2 / 0 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.