@definitelytyped/dts-critic
Checks a new .d.ts against the Javascript source and tells you what problems it has
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft DefinitelyTyped-tools monorepo; provenance not currently attested but package is well-established and trusted. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.1.32 | 3 / 0 | |
| 0.1.31 | 3 / 0 | |
| 0.1.30 | 3 / 0 | |
| 0.1.29 | 3 / 0 | |
| 0.1.28 | 3 / 0 | |
| 0.1.27 | 3 / 0 | |
| 0.1.26 | 3 / 0 | |
| 0.1.25 | 3 / 0 | |
| 0.1.24 | 3 / 0 | |
| 0.1.23 | 3 / 0 | |
| 0.1.22 | 3 / 0 | |
| 0.1.21 | 3 / 0 | |
| 0.1.20 | 3 / 0 | |
| 0.1.19 | 3 / 0 | |
| 0.1.18 | 3 / 0 | |
| 0.1.17 | 3 / 0 | |
| 0.1.16 | 3 / 0 | |
| 0.1.15 | 3 / 0 | |
| 0.1.14 | 3 / 0 | |
| 0.1.13 | 3 / 0 | |
| 0.1.12 | 3 / 0 | |
| 0.1.11 | 3 / 0 |
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.