← Home

@feathersjs/koa

45
Versions
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

dafflmarshallswain

Keywords

featherskoajs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 45 of 45)

Version Deps Published
5.0.46 15 / 11
5.0.45 15 / 11
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
5.0.33 15 / 11
5.0.32 15 / 11
5.0.31 15 / 11
5.0.30 15 / 11
5.0.29 15 / 11
5.0.28 15 / 11
5.0.27 15 / 11
5.0.26 15 / 11
5.0.25 15 / 11
5.0.24 15 / 11
5.0.23 15 / 11
5.0.22 15 / 11
5.0.21 15 / 11
5.0.20 15 / 11
5.0.19 15 / 11
5.0.18 15 / 11
5.0.17 15 / 11
5.0.16 15 / 11
5.0.15 15 / 11
5.0.14 15 / 11
5.0.13 15 / 11
5.0.12 15 / 11
5.0.11 15 / 11
5.0.10 15 / 11
5.0.9 15 / 11
5.0.8 15 / 11
5.0.7 15 / 11
5.0.6 15 / 11
5.0.5 15 / 11
5.0.4 15 / 11
5.0.3 15 / 11
5.0.1 15 / 11
5.0.0 16 / 11

v5.0.46

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: marshallswain → daffl (on 2026-06-27, known maintainer) provenance

This version was published by a different npm account (daffl) than the most recent previously approved version (marshallswain) on 2026-06-27, but daffl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v5.0.33

1 finding
LOW No provenance attestation provenance

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

v5.0.32

1 finding
LOW No provenance attestation provenance

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

v5.0.31

1 finding
LOW No provenance attestation provenance

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

v5.0.30

1 finding
LOW No provenance attestation provenance

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

v5.0.29

1 finding
LOW No provenance attestation provenance

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

v5.0.28

1 finding
LOW No provenance attestation provenance

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

v5.0.27

1 finding
LOW No provenance attestation provenance

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

v5.0.26

1 finding
LOW No provenance attestation provenance

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

v5.0.25

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.

v5.0.24

1 finding
LOW No provenance attestation provenance

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

v5.0.23

1 finding
LOW No provenance attestation provenance

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

v5.0.22

1 finding
LOW No provenance attestation provenance

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

v5.0.21

1 finding
LOW No provenance attestation provenance

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

v5.0.20

1 finding
LOW No provenance attestation provenance

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

v5.0.19

1 finding
LOW No provenance attestation provenance

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

v5.0.18

1 finding
LOW No provenance attestation provenance

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

v5.0.17

1 finding
LOW No provenance attestation provenance

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

v5.0.16

1 finding
LOW No provenance attestation provenance

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

v5.0.15

1 finding
LOW No provenance attestation provenance

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

v5.0.14

1 finding
LOW No provenance attestation provenance

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

v5.0.13

1 finding
LOW No provenance attestation provenance

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

v5.0.12

1 finding
LOW No provenance attestation provenance

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

v5.0.11

1 finding
LOW No provenance attestation provenance

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

v5.0.10

1 finding
LOW No provenance attestation provenance

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

v5.0.9

1 finding
LOW No provenance attestation provenance

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

v5.0.8

1 finding
LOW No provenance attestation provenance

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

v5.0.7

1 finding
LOW No provenance attestation provenance

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

v5.0.6

1 finding
LOW No provenance attestation provenance

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

v5.0.5

1 finding
LOW No provenance attestation provenance

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

v5.0.4

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

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

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