@definitelytyped/dtslint-runner
Run dtslint on DefinitelyTyped packages
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft-maintained package; provenance absence is consistent across all versions of this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.1.52 | 5 / 1 | |
| 0.1.51 | 5 / 1 | |
| 0.1.50 | 5 / 1 | |
| 0.1.49 | 5 / 1 | |
| 0.1.48 | 5 / 1 | |
| 0.1.47 | 5 / 1 | |
| 0.1.46 | 5 / 1 | |
| 0.1.45 | 5 / 1 | |
| 0.1.44 | 5 / 1 | |
| 0.1.43 | 5 / 1 | |
| 0.1.42 | 5 / 1 | |
| 0.1.41 | 5 / 1 | |
| 0.1.40 | 5 / 1 | |
| 0.1.39 | 5 / 1 | |
| 0.1.38 | 5 / 1 | |
| 0.1.37 | 5 / 1 | |
| 0.1.36 | 5 / 1 | |
| 0.1.35 | 5 / 1 | |
| 0.1.34 | 5 / 1 | |
| 0.1.33 | 5 / 1 | |
| 0.1.32 | 5 / 1 | |
| 0.1.31 | 5 / 1 | |
| 0.1.30 | 5 / 1 | |
| 0.1.29 | 5 / 1 | |
| 0.1.28 | 5 / 1 | |
| 0.1.27 | 5 / 1 | |
| 0.1.26 | 5 / 1 | |
| 0.1.25 | 5 / 1 | |
| 0.1.24 | 5 / 1 |
v0.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.