@feathersjs/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @feathersjs/koa is part of the official FeathersJS monorepo; levenshtein match against 'got' is a false positive for scoped packages. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @feathersjs/koa is part of the official FeathersJS monorepo; levenshtein match against 'joi' is a false positive for scoped packages. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @feathersjs/koa is part of the official FeathersJS monorepo; levenshtein match against 'zod' is a false positive for scoped packages. | ai | |
| phantom-deps | phantom-dep:@types/koa | AI (phantom-deps): @types/* packages are TypeScript type definitions legitimately declared in dependencies for downstream consumers; not directly imported in source by design. | ai | |
| phantom-deps | phantom-dep:@types/koa-qs | AI (phantom-deps): @types/* packages are TypeScript type definitions legitimately declared in dependencies for downstream consumers; not directly imported in source by design. | ai | |
| phantom-deps | phantom-dep:@types/koa__cors | AI (phantom-deps): @types/* packages are TypeScript type definitions legitimately declared in dependencies for downstream consumers; not directly imported in source by design. | ai | |
| phantom-deps | phantom-dep:@types/koa-static | AI (phantom-deps): @types/* packages are TypeScript type definitions legitimately declared in dependencies for downstream consumers; not directly imported in source by design. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.0.44 | 15 / 11 | |
| 5.0.43 | 15 / 11 | |
| 5.0.42 | 15 / 11 | |
| 5.0.41 | 15 / 11 | |
| 5.0.40 | 15 / 11 | |
| 5.0.39 | 15 / 11 | |
| 5.0.37 | 15 / 11 | |
| 5.0.36 | 15 / 11 | |
| 5.0.35 | 15 / 11 | |
| 5.0.34 | 15 / 11 |
v5.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.