@autorest/openapi-to-typespec
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typespec/compiler | AI (phantom-deps): TypeSpec toolchain deps referenced in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@typespec/openapi3 | AI (phantom-deps): TypeSpec toolchain deps referenced in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@azure-tools/typespec-autorest | AI (phantom-deps): TypeSpec toolchain deps referenced in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@typespec/prettier-plugin-typespec | AI (phantom-deps): TypeSpec toolchain deps referenced in config; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@azure-tools/openapi | AI (dependencies): Official Azure-tools org package, same publisher family as this repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Normal cadence for this Autorest sub-package under active azure-sdk maintainer. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 9 / 37 | |
| 0.10.14 | 9 / 37 | |
| 0.10.13 | 10 / 36 | |
| 0.10.12 | 10 / 35 | |
| 0.10.11 | 18 / 27 | |
| 0.10.10 | 17 / 28 | |
| 0.10.9 | 17 / 28 | |
| 0.10.8 | 17 / 28 | |
| 0.10.7 | 17 / 28 | |
| 0.10.6 | 17 / 27 | |
| 0.10.5 | 17 / 27 | |
| 0.10.4 | 17 / 27 | |
| 0.10.3 | 17 / 27 | |
| 0.10.2 | 17 / 27 | |
| 0.10.1 | 17 / 27 | |
| 0.10.0 | 17 / 26 | |
| 0.9.1 | 17 / 26 | |
| 0.9.0 | 17 / 26 |
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.