@unctad-ai/voice-agent
Meta-package for voice-agent-kit client packages — installs core, registries, and ui in one dependency
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@unctad-ai/voice-agent-ui | AI (phantom-deps): Meta-package; dependencies are declared and re-exported implicitly. | ai | |
| phantom-deps | phantom-dep:@unctad-ai/voice-agent-core | AI (phantom-deps): Meta-package; dependencies are declared and re-exported implicitly. | ai | |
| phantom-deps | phantom-dep:@unctad-ai/voice-agent-registries | AI (phantom-deps): Meta-package; dependencies are declared and re-exported implicitly. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.5.0 | 3 / 0 | |
| 5.4.8 | 3 / 0 | |
| 5.4.7 | 3 / 0 | |
| 5.4.6 | 3 / 0 | |
| 5.4.5 | 3 / 0 | |
| 5.4.4 | 3 / 0 | |
| 5.4.3 | 3 / 0 | |
| 5.4.2 | 3 / 0 | |
| 5.4.1 | 3 / 0 | |
| 5.4.0 | 3 / 0 |
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.