← Home

@types/koa-compose

npm Repository Homepage

TypeScript definitions for koa-compose

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:https://github.com/jkeylu AI (email-domain): The 'email' field contains a GitHub profile URL, not an email address. The analyzer is misinterpreting a URL as a domain — no real domain hijacking risk exists. This is a stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): No keywords, no runtime deps, and tiny payload are all expected characteristics of a @types/* TypeScript definitions package. These signals are structural false positives for this package type. ai

Versions (showing 13 of 13)

Version Deps Published
3.2.9 1 / 0
3.2.8 1 / 0
3.2.7 1 / 0
3.2.6 1 / 0
3.2.5 1 / 0
3.2.4 1 / 0
3.2.3 1 / 0
3.2.2 0 / 0
3.2.1 0 / 0
3.2.0 0 / 0
3.0.30 0 / 0
3.0.29 0 / 0
3.0.28 0 / 0

v3.2.9

1 finding
LOW No provenance attestation provenance

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

v3.2.8

1 finding
LOW No provenance attestation provenance

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

v3.2.7

1 finding
LOW No provenance attestation provenance

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

v3.2.6

1 finding
LOW No provenance attestation provenance

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

v3.2.5

1 finding
LOW No provenance attestation provenance

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

v3.2.4

1 finding
LOW No provenance attestation provenance

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

v3.2.3

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

1 finding
LOW No provenance attestation provenance

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

v3.0.29

1 finding
LOW No provenance attestation provenance

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

v3.0.28

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/jkeylu email-domain

Maintainer email 'https://github.com/jkeylu' uses domain 'https://github.com/jkeylu' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.