← Home

@azure-tools/typespec-go

TypeSpec emitter for Go SDKs

23
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

Keywords

gogolangtypespec

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@azure-tools/linq AI (dependencies): Same Azure Tools namespace as the publisher; stable dependency pattern for this package family. ai
provenance no-provenance AI (provenance): Established Microsoft/Azure publisher; lack of Sigstore attestation is common and not a risk signal here. ai

Versions (showing 23 of 23)

Version Deps Published
0.15.0 1 / 26
0.14.3 2 / 28
0.14.2 2 / 28
0.14.1 2 / 28
0.14.0 2 / 28
0.13.0 2 / 28
0.12.0 2 / 28
0.11.2 2 / 28
0.11.1 2 / 28
0.11.0 2 / 27
0.10.7 2 / 27
0.10.6 2 / 27
0.10.5 2 / 26
0.10.4 2 / 26
0.10.3 2 / 26
0.10.2 2 / 26
0.10.1 2 / 26
0.10.0 2 / 26
0.9.2 2 / 26
0.9.0 3 / 25
0.8.8 3 / 25
0.8.5 3 / 25
0.4.12 3 / 24

v0.15.0

2 findings
INFO No provenance attestation provenance

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

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

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (azure-sdk) on 2026-07-17, 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.14.3

1 finding
INFO No provenance attestation provenance

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