@azure-tools/typespec-python
TypeSpec emitter for Python SDKs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Both azure-sdk and microsoft1es are Microsoft-controlled npm accounts; org-level transition, not a compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package is published by Microsoft's azure-sdk account with strong track record. Dormancy followed by resumption is consistent with SDK toolchain versioning cycles, not account takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Azure SDK package; lack of Sigstore provenance is common and not a meaningful risk signal for this publisher. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is declared in dependencies and used in eng/scripts; phantom-dep detection is a false positive here. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Install script sets up a Python virtual environment for the Python SDK generator — a documented, stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is declared in dependencies and used in eng/scripts; phantom-dep detection is a false positive here. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in run-python3.ts to invoke Python for the SDK generator setup — not malicious, consistent with the package's documented purpose. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is declared in dependencies and used in eng/scripts (included in published files); phantom-dep detection is a false positive here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.62.0 | 3 / 27 | |
| 0.61.3 | 5 / 33 | |
| 0.61.2 | 5 / 31 | |
| 0.61.1 | 5 / 31 | |
| 0.60.2 | 5 / 31 | |
| 0.59.3 | 5 / 31 | |
| 0.59.2 | 5 / 31 | |
| 0.59.1 | 5 / 31 | |
| 0.57.1 | 5 / 31 | |
| 0.56.0 | 5 / 31 | |
| 0.55.0 | 5 / 31 | |
| 0.53.2 | 5 / 31 | |
| 0.53.0 | 5 / 31 | |
| 0.52.2 | 5 / 31 | |
| 0.49.0 | 5 / 31 | |
| 0.48.2 | 5 / 31 | |
| 0.48.1 | 5 / 31 | |
| 0.48.0 | 5 / 31 | |
| 0.45.2 | 5 / 31 | |
| 0.45.0 | 5 / 30 | |
| 0.44.2 | 5 / 30 |
v0.62.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.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.
v0.55.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.
v0.53.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.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.
v0.52.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.