@definitelytyped/dtslint
Runs tests on TypeScript definition files
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.2.47 | 15 / 3 | |
| 0.2.46 | 15 / 3 | |
| 0.2.45 | 15 / 3 | |
| 0.2.44 | 15 / 3 | |
| 0.2.43 | 15 / 3 | |
| 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 | |
| 0.2.32 | 15 / 4 | |
| 0.2.31 | 15 / 4 | |
| 0.2.30 | 15 / 4 | |
| 0.2.29 | 15 / 4 | |
| 0.2.28 | 15 / 4 | |
| 0.2.27 | 15 / 4 | |
| 0.2.26 | 15 / 4 | |
| 0.2.25 | 15 / 4 | |
| 0.2.24 | 15 / 4 | |
| 0.2.23 | 15 / 4 | |
| 0.2.22 | 15 / 4 | |
| 0.2.21 | 15 / 4 |
v0.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.