All @mastra/ai-sdk versions

@mastra/ai-sdk @0.3.1

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
25
Risk Score
Apache-2.0
License
No
Install Scripts
1
Dependencies
9
Dev Dependencies
59.2 KB
Package Size
Published

Adds custom API routes to be compatible with the AI SDK UI parts

Maintainers

smthomasabhiaiyerifedayoadeleke5140taofeeq-deruehinderocalcsamrase-wardpeettylerbarnesnikaiyer

Keywords

mastraai-sdkai

Dependencies (1)

PackageConstraintRegistry Status
ai ^5.0.60 auto_approved

Dev Dependencies (9)

PackageConstraintRegistry Status
zod ^3.25.76 auto_approved
tsup ^8.5.0 auto_approved
eslint ^9.37.0 auto_approved
vitest ^3.2.4 No greenflagged match
typescript ^5.8.3 auto_approved
@mastra/core 0.24.5 No greenflagged match
@internal/lint 0.0.63 Not imported
@types/json-schema ^7.0.15 auto_approved
@internal/types-builder 0.0.38 Not imported

Transitive Dependency Tree

9 transitive deps max depth 5
├─ ai ^5.0.60 → 5.0.193
  ├─ @ai-sdk/gateway 2.0.94 → 2.0.94
  ├─ @ai-sdk/provider 2.0.3 → 2.0.3
  ├─ @ai-sdk/provider-utils 3.0.25 → 3.0.25
├─ @opentelemetry/api 1.9.0 → 1.9.0
  ├─ @ai-sdk/provider 2.0.3 → 2.0.3
  ├─ @ai-sdk/provider-utils 3.0.25 → 3.0.25
  ├─ @standard-schema/spec ^1.0.0 → 1.1.0
  ├─ @vercel/oidc 3.1.0 → 3.1.0
  ├─ eventsource-parser ^3.0.6 → 3.1.0
├─ json-schema ^0.4.0 → 0.4.0
  ├─ @ai-sdk/provider 2.0.3 → 2.0.3
  ├─ @standard-schema/spec ^1.0.0 → 1.1.0
  ├─ eventsource-parser ^3.0.6 → 3.1.0
├─ json-schema ^0.4.0 → 0.4.0
  ├─ json-schema ^0.4.0 → 0.4.0

Changes from v1.0.1

No metadata changes detected.

File Changes

0 added 0 removed 7 modified size delta: +2.6 KB

Risk Dispositions (1 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
regressed-provenance provenance reject AI AI (provenance): Provenance regression is a disqualifying signal for this package until attestation is restored.

SAST Findings (1)

HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

Review Summary

Risk score: 25. Findings: 1 high (+25).

Published to npm: