llama-stack-client
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Build utility script resolving package.json path; not runtime user-facing code. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types packages are type-only, never directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/node-fetch | AI (phantom-deps): @types packages are type-only, never directly imported at runtime. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 7 / 16 | |
| 0.4.3 | 7 / 0 | |
| 0.4.2 | 7 / 0 | |
| 0.4.1 | 7 / 0 | |
| 0.4.0 | 7 / 0 | |
| 0.3.5 | 7 / 0 | |
| 0.3.4 | 7 / 0 | |
| 0.3.3 | 7 / 0 | |
| 0.3.2 | 7 / 0 | |
| 0.3.1 | 7 / 0 | |
| 0.3.0 | 7 / 0 | |
| 0.2.23 | 7 / 0 | |
| 0.2.22 | 7 / 0 | |
| 0.2.21 | 7 / 0 | |
| 0.2.20 | 7 / 0 | |
| 0.2.19 | 7 / 0 | |
| 0.2.18 | 7 / 0 | |
| 0.2.17 | 7 / 0 | |
| 0.2.16 | 7 / 0 | |
| 0.2.15 | 7 / 0 | |
| 0.2.14 | 7 / 0 | |
| 0.2.13 | 8 / 0 | |
| 0.2.12 | 8 / 0 | |
| 0.2.11 | 8 / 0 | |
| 0.2.10 | 8 / 0 | |
| 0.2.9 | 8 / 0 | |
| 0.2.8 | 8 / 0 | |
| 0.2.7 | 8 / 0 |
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.