← Home

@types/execa

npm

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

10
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
bogus-package bogus-package AI (bogus-package): This is a legitimate @types/ stub package from DefinitelyTyped. Tiny payload, no README code, and no repo URL are all expected for deprecated stub type definitions. ai
phantom-deps phantom-dep:execa AI (phantom-deps): The execa dependency is intentional — it's a redirect dependency so installing this stub also pulls in the real execa package with its bundled types. ai

Versions (showing 10 of 10)

Version Deps Published
2.0.2 1 / 0
2.0.1 1 / 0
2.0.0 1 / 0
0.9.0 1 / 0
0.8.1 1 / 0
0.8.0 1 / 0
0.7.2 1 / 0
0.7.1 1 / 0
0.7.0 1 / 0
0.6.0 1 / 0

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.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.

v0.8.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.

v0.7.2

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.

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

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

v0.6.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.