← Home

@definitelytyped/definitions-parser

npm Repository Homepage

Reads the DefinitelyTyped repository and provides an API for querying its metadata

9
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

microsoft1esandrewbranchtypessanders_nweswighamdefinitelytyped-publisherjakebailey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only ambient dep; not directly imported by convention in TS projects. ai
phantom-deps phantom-dep:@types/semver AI (phantom-deps): @types/semver is a type-only ambient dep; not directly imported by convention in TS projects. ai
bogus-package bogus-package AI (bogus-package): Internal tooling package for DefinitelyTyped; sparse README and no keywords are expected for org-internal tooling. ai

Versions (showing 9 of 9)

Version Deps Published
0.1.31 7 / 2
0.1.30 7 / 2
0.1.29 7 / 2
0.1.28 7 / 2
0.1.27 7 / 2
0.1.26 7 / 2
0.1.25 7 / 2
0.1.24 7 / 2
0.1.23 7 / 2

v0.1.31

1 finding
LOW No provenance attestation provenance

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

v0.1.30

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

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

v0.1.27

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

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

v0.1.24

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

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.