@azure-tools/typespec-client-generator-core
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 | publisher-changed | AI (provenance): microsoft1es is a trusted Microsoft org account; transition from azure-sdk is a known MS internal migration pattern. | ai |
Versions (showing 100 of 110)
| Version | Deps | Published |
|---|---|---|
| 0.70.0 | 3 / 20 | |
| 0.69.2 | 3 / 20 | |
| 0.69.1 | 3 / 20 | |
| 0.69.0 | 3 / 20 | |
| 0.68.4 | 3 / 20 | |
| 0.68.3 | 3 / 20 | |
| 0.68.2 | 3 / 20 | |
| 0.68.1 | 3 / 20 | |
| 0.68.0 | 3 / 20 | |
| 0.67.4 | 3 / 21 | |
| 0.67.3 | 3 / 21 | |
| 0.67.2 | 3 / 21 | |
| 0.67.1 | 3 / 21 | |
| 0.67.0 | 3 / 21 | |
| 0.66.4 | 3 / 21 | |
| 0.66.3 | 3 / 21 | |
| 0.66.2 | 3 / 21 | |
| 0.66.1 | 3 / 21 | |
| 0.66.0 | 3 / 21 | |
| 0.65.4 | 3 / 21 | |
| 0.65.3 | 3 / 21 | |
| 0.65.2 | 3 / 21 | |
| 0.65.1 | 3 / 21 | |
| 0.65.0 | 3 / 21 | |
| 0.64.6 | 3 / 21 | |
| 0.64.5 | 3 / 21 | |
| 0.64.4 | 3 / 21 | |
| 0.64.3 | 3 / 21 | |
| 0.64.2 | 3 / 21 | |
| 0.64.1 | 3 / 21 | |
| 0.64.0 | 3 / 21 | |
| 0.63.4 | 3 / 21 | |
| 0.63.3 | 3 / 21 | |
| 0.63.2 | 3 / 21 | |
| 0.63.1 | 3 / 21 | |
| 0.63.0 | 3 / 21 | |
| 0.62.0 | 3 / 21 | |
| 0.61.3 | 3 / 21 | |
| 0.61.2 | 3 / 21 | |
| 0.61.1 | 3 / 21 | |
| 0.61.0 | 3 / 21 | |
| 0.60.3 | 3 / 21 | |
| 0.60.2 | 3 / 21 | |
| 0.60.1 | 3 / 21 | |
| 0.60.0 | 3 / 21 | |
| 0.59.1 | 3 / 21 | |
| 0.59.0 | 3 / 21 | |
| 0.58.2 | 3 / 21 | |
| 0.58.1 | 3 / 21 | |
| 0.58.0 | 3 / 21 | |
| 0.57.3 | 3 / 21 | |
| 0.57.2 | 3 / 21 | |
| 0.57.1 | 3 / 21 | |
| 0.57.0 | 3 / 21 | |
| 0.56.4 | 3 / 21 | |
| 0.56.3 | 3 / 21 | |
| 0.56.2 | 3 / 21 | |
| 0.56.1 | 3 / 21 | |
| 0.56.0 | 3 / 21 | |
| 0.55.1 | 3 / 21 | |
| 0.55.0 | 3 / 21 | |
| 0.54.2 | 3 / 21 | |
| 0.54.1 | 3 / 21 | |
| 0.54.0 | 3 / 21 | |
| 0.53.1 | 3 / 21 | |
| 0.53.0 | 3 / 21 | |
| 0.52.0 | 3 / 18 | |
| 0.51.3 | 3 / 18 | |
| 0.51.2 | 3 / 18 | |
| 0.51.1 | 3 / 18 | |
| 0.51.0 | 3 / 18 | |
| 0.50.3 | 3 / 18 | |
| 0.50.2 | 3 / 18 | |
| 0.50.1 | 3 / 18 | |
| 0.50.0 | 3 / 18 | |
| 0.49.1 | 3 / 18 | |
| 0.49.0 | 3 / 18 | |
| 0.48.6 | 2 / 18 | |
| 0.48.5 | 2 / 18 | |
| 0.48.4 | 2 / 18 | |
| 0.48.3 | 2 / 18 | |
| 0.48.2 | 2 / 18 | |
| 0.48.1 | 2 / 18 | |
| 0.48.0 | 2 / 18 | |
| 0.47.4 | 2 / 18 | |
| 0.47.3 | 2 / 18 | |
| 0.47.2 | 2 / 18 | |
| 0.47.1 | 2 / 18 | |
| 0.47.0 | 2 / 18 | |
| 0.46.2 | 2 / 18 | |
| 0.46.1 | 2 / 18 | |
| 0.46.0 | 2 / 18 | |
| 0.45.4 | 2 / 17 | |
| 0.45.3 | 2 / 17 | |
| 0.45.2 | 2 / 17 | |
| 0.45.1 | 2 / 17 | |
| 0.45.0 | 2 / 17 | |
| 0.44.3 | 2 / 17 | |
| 0.44.2 | 2 / 17 | |
| 0.44.1 | 2 / 17 |
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.