@mastra/voice-cloudflare
Mastra Cloudflare AI voice integration
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:easy-day-js | AI (phantom-deps): Phantom-dep rule cannot auto-block per policy; flagged in rationale for human review. | ai | |
| source-diff | obfuscated-file:dist/_types/@internal_voice/dist/_types/@internal_ai-sdk-v5/dist/index.d.ts | AI (source-diff): Generated TypeScript declaration bundle; long lines are normal for bundled .d.ts files, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Size increase driven by bundled internal type declarations from monorepo packages, not injected payloads. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Explained by inclusion of bundled .d.ts type files from internal monorepo dependencies. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared and used in validation; false positive for TypeScript packages. | ai | |
| dependencies | unvetted-dep:cloudflare | AI (dependencies): cloudflare SDK is the expected runtime dep for a Cloudflare AI voice integration package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.12.2 | 2 / 11 | |
| 0.12.0 | 1 / 12 | |
| 0.11.12 | 1 / 11 | |
| 0.11.11 | 1 / 11 | |
| 0.11.10 | 1 / 11 | |
| 0.11.9 | 1 / 11 | |
| 0.11.8 | 1 / 11 | |
| 0.11.7 | 1 / 11 | |
| 0.11.6 | 1 / 11 | |
| 0.11.5 | 1 / 11 | |
| 0.11.4 | 1 / 11 | |
| 0.11.3 | 1 / 11 | |
| 0.11.2 | 1 / 11 | |
| 0.10.8 | 2 / 10 | |
| 0.10.7 | 2 / 10 | |
| 0.10.6 | 2 / 9 | |
| 0.10.5 | 2 / 9 | |
| 0.10.4 | 2 / 9 | |
| 0.10.3 | 2 / 9 | |
| 0.10.2 | 2 / 9 | |
| 0.10.1 | 2 / 9 | |
| 0.10.0 | 2 / 9 | |
| 0.1.11 | 3 / 8 | |
| 0.1.10 | 3 / 8 | |
| 0.1.9 | 3 / 8 | |
| 0.1.8 | 3 / 8 |
v0.12.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.