@typespec/json-schema
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 TypeSpec monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.14.0 | 2 / 12 | |
| 1.13.0 | 2 / 12 | |
| 1.12.0 | 2 / 12 | |
| 1.11.0 | 2 / 13 | |
| 1.10.0 | 2 / 13 | |
| 1.9.0 | 2 / 13 | |
| 1.8.0 | 2 / 13 | |
| 1.7.0 | 2 / 13 | |
| 1.6.0 | 2 / 13 | |
| 1.5.0 | 2 / 13 | |
| 1.4.0 | 2 / 13 | |
| 1.3.0 | 2 / 13 | |
| 1.2.1 | 2 / 13 | |
| 1.2.0 | 2 / 13 | |
| 1.1.0 | 2 / 13 | |
| 1.0.0 | 2 / 13 |
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.