← Home

@mastra/voice-google

npm Repository Homepage

Mastra Google voice integration

43
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

abhiaiyersmthomasrase-calcsamnikaiyertylerbarneswardpeet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 type rollups, not obfuscation. ai

Versions (showing 43 of 43)

Version Deps Published
0.14.0 2 / 11
0.13.0 2 / 11
0.12.2 2 / 11
0.12.1 2 / 10
0.11.12 2 / 8
0.11.11 2 / 8
0.11.10 2 / 8
0.11.9 2 / 8
0.11.8 2 / 8
0.11.7 2 / 8
0.11.6 2 / 8
0.11.5 2 / 8
0.11.4 2 / 8
0.11.3 2 / 8
0.11.2 2 / 8
0.10.8 3 / 8
0.10.7 3 / 8
0.10.6 3 / 7
0.10.5 3 / 7
0.10.4 3 / 7
0.10.3 3 / 7
0.10.2 3 / 7
0.10.1 3 / 7
0.10.0 3 / 7
0.1.18 4 / 6
0.1.17 4 / 6
0.1.16 4 / 6
0.1.15 4 / 6
0.1.14 4 / 6
0.1.13 4 / 6
0.1.12 4 / 6
0.1.11 4 / 6
0.1.10 4 / 6
0.1.9 4 / 6
0.1.8 4 / 6
0.1.7 4 / 6
0.1.6 4 / 6
0.1.5 4 / 6
0.1.4 4 / 6
0.1.3 4 / 6
0.1.2 4 / 6
0.1.1 4 / 6
0.1.0 4 / 6

v0.14.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.