← Home

@azure-tools/typespec-client-generator-cli

A tool to generate Azure SDKs from TypeSpec

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

azure-sdkmicrosoft1esazure-powershell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@autorest/openapi-to-typespec AI (dependencies): First-party Azure tooling package, pinned version. ai
dependencies unvetted-dep:@autorest/csharp AI (dependencies): First-party Microsoft/Azure tooling dependency, fetched via official aka.ms redirect. ai
phantom-deps phantom-dep:@autorest/csharp AI (phantom-deps): Referenced via config files as documented in this CLI's design. ai
npm-metadata url-dep:@autorest/csharp AI (npm-metadata): aka.ms is an official Microsoft URL shortener, consistent across Azure tooling. ai
phantom-deps phantom-dep:@azure-tools/rest-api-diff AI (phantom-deps): Same org scope; referenced indirectly as expected for this toolchain. ai
phantom-deps phantom-dep:@autorest/openapi-to-typespec AI (phantom-deps): Referenced in config files; not a direct import, expected for this tool. ai
phantom-deps phantom-dep:autorest AI (phantom-deps): autorest is a CLI tool invoked by config, not imported directly; expected for this SDK gen tool. ai
phantom-deps phantom-dep:@autorest/core AI (phantom-deps): Referenced in config files as documented; not a direct import. ai
phantom-deps phantom-dep:@types/yargs AI (phantom-deps): Type definitions loaded by yargs convention; stable pattern for this package. ai
bogus-package bogus-package AI (bogus-package): Tool package with GitHub-hosted docs; README links are legitimate references, not phishing. ai
phantom-deps phantom-dep:@azure/core-rest-pipeline AI (phantom-deps): Azure SDK framework-scoped dependency; loaded by convention in Azure tools. ai

Versions (showing 21 of 21)

Version Deps Published
0.33.1 11 / 11
0.33.0 9 / 11
0.32.1 9 / 11
0.32.0 9 / 11
0.29.1 12 / 11
0.28.2 12 / 11
0.28.1 12 / 11
0.28.0 12 / 11
0.27.0 12 / 11
0.23.0 12 / 11
0.22.0 13 / 11
0.21.0 13 / 11
0.11.2 13 / 12
0.10.0 10 / 12
0.9.3 9 / 11
0.9.2 6 / 11
0.9.1 6 / 11
0.9.0 6 / 11
0.8.1 6 / 11
0.8.0 6 / 11
0.7.1 6 / 11

v0.11.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: azure-sdk → microsoft1es (on 2024-07-03, known maintainer) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (azure-sdk) on 2024-07-03, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: azure-sdk → microsoft1es (on 2024-06-21, known maintainer) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (azure-sdk) on 2024-06-21, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.