← Home

@types/commander

npm

Stub TypeScript definitions entry for commander, which provides its own types definitions

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:http://github.com/mdezem AI (email-domain): The 'email' field contains a GitHub profile URL, not an email address. The analyzer is misinterpreting a URL as an email domain. No actual domain hijacking risk exists. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a standard type-only dependency in DefinitelyTyped packages; not directly imported by convention. Stable false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
2.12.5 1 / 0
2.12.4 1 / 0
2.12.3 1 / 0
2.12.2 1 / 0
2.12.0 1 / 0
2.11.0 1 / 0
2.9.2 1 / 0
2.9.1 1 / 0
2.9.0 1 / 0
2.3.31 1 / 0
2.3.30 1 / 0
2.3.29 1 / 0
2.3.28 1 / 0

v2.12.5

1 finding
LOW No provenance attestation provenance

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

v2.12.4

1 finding
LOW No provenance attestation provenance

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

v2.12.3

1 finding
LOW No provenance attestation provenance

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

v2.12.2

1 finding
LOW No provenance attestation provenance

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

v2.12.0

1 finding
LOW No provenance attestation provenance

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

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.9.2

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

v2.9.0

1 finding
LOW No provenance attestation provenance

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

v2.3.31

1 finding
LOW No provenance attestation provenance

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

v2.3.30

1 finding
LOW No provenance attestation provenance

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

v2.3.29

2 findings
HIGH Unclaimed maintainer email domain: http://github.com/mdezem email-domain

Maintainer email 'http://github.com/mdezem' uses domain 'http://github.com/mdezem' 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. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.28

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.