← Home

@definitelytyped/dtslint

npm Repository Homepage

Runs tests on TypeScript definition files

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

microsoft1esandrewbranchtypessanders_nweswighamdefinitelytyped-publisherjakebailey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:eslint AI (typosquat): Legitimate Microsoft DefinitelyTyped tooling package; not a typosquat of eslint. ai
phantom-deps phantom-dep:eslint-plugin-import AI (phantom-deps): ESLint plugins are referenced in config files, not directly imported — expected pattern for this linting tool. ai
phantom-deps phantom-dep:@typescript-eslint/types AI (phantom-deps): Referenced in ESLint config, not directly imported — stable false positive for this package. ai
phantom-deps phantom-dep:@typescript-eslint/utils AI (phantom-deps): Referenced in ESLint config, not directly imported — stable false positive for this package. ai
phantom-deps phantom-dep:@typescript-eslint/parser AI (phantom-deps): Referenced in ESLint config, not directly imported — stable false positive for this package. ai
phantom-deps phantom-dep:@typescript-eslint/eslint-plugin AI (phantom-deps): Referenced in ESLint config, not directly imported — stable false positive for this package. ai
phantom-deps phantom-dep:@typescript-eslint/typescript-estree AI (phantom-deps): Referenced in ESLint config, not directly imported — stable false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.42 15 / 3
0.2.41 15 / 3
0.2.40 15 / 3
0.2.39 15 / 3
0.2.38 15 / 4
0.2.37 15 / 4
0.2.36 15 / 4
0.2.35 15 / 4
0.2.34 15 / 4
0.2.33 15 / 4

v0.2.42

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

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

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

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

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

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

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

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

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

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.