@typespec/http-client-python
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): azure-sdk → microsoft1es is an intra-Microsoft account transition; both accounts are Microsoft-controlled. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; low risk without Sigstore attestation given publisher trust. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): azure-sdk publisher has strong track record (1007 approved); dormancy likely reflects TypeSpec release cadence, not account takeover. Official Microsoft repo confirmed. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Install script sets up Python virtual environment for code generation — core functionality of this TypeSpec Python emitter. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is listed as a direct runtime dependency in package.json; phantom-dep finding is a false positive for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread in CI/build scripts to pass PATH-augmented environment to child processes is standard build tooling practice for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to invoke Python scripts — core functionality of a Python SDK code generator. Expected and stable for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.29.0 | 5 / 27 | |
| 0.28.3 | 5 / 27 | |
| 0.28.1 | 5 / 27 | |
| 0.26.2 | 5 / 27 | |
| 0.21.0 | 5 / 27 | |
| 0.20.3 | 5 / 27 | |
| 0.20.2 | 5 / 27 | |
| 0.20.1 | 5 / 27 | |
| 0.20.0 | 5 / 27 | |
| 0.19.2 | 5 / 27 | |
| 0.13.0 | 5 / 27 | |
| 0.12.5 | 5 / 27 | |
| 0.12.4 | 5 / 27 | |
| 0.12.2 | 5 / 27 | |
| 0.12.1 | 5 / 27 | |
| 0.12.0 | 5 / 27 | |
| 0.11.3 | 5 / 27 |
v0.29.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.28.3
6 findingsScript: tsx ./eng/scripts/setup/install.ts
Spreading entire process.env into an object — may capture all secrets 81 | join(monorepoRoot, "node_modules", ".bin"), 82 | ].join(pathSep); > 83 | const env = { 84 | ...process.env, 85 | PATH: `${binPaths}${pathSep}${process.env.PATH}`,
Spreading entire process.env into an object — may capture all secrets 99 | join(monorepoRoot, "node_modules"), 100 | ].join(pathSep); > 101 | const env = { 102 | ...process.env, 103 | PATH: `${binPaths}${pathSep}${process.env.PATH}`,
Spreading entire process.env into an object — may capture all secrets 97 | cwd: testsDir, 98 | stdio: !argv.values.quiet ? "inherit" : "pipe", > 99 | env: { ...process.env, FOLDER: env.split("-")[1] || "azure" }, 100 | }); 101 |
Spreading entire process.env into an object — may capture all secrets 225 | join(monorepoRoot, "node_modules", ".bin"), 226 | ].join(pathSep); > 227 | const env = { 228 | ...process.env, 229 | PATH: `${binPaths}${pathSep}${process.env.PATH}`,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.