@mastra/arize @1.2.3
Arize observability provider for Mastra - includes tracing and future observability features
Maintainers
Dependencies (9)
| Package | Constraint | Registry Status |
|---|---|---|
| easy-day-js | ^1.11.21 | auto_approved |
| @opentelemetry/core | ^2.7.1 | auto_approved |
| @mastra/otel-exporter | 1.2.2 | auto_approved |
| @opentelemetry/resources | ^2.7.1 | auto_approved |
| @arizeai/openinference-genai | 0.1.7 | auto_approved |
| @opentelemetry/sdk-trace-base | ^2.7.1 | auto_approved |
| @opentelemetry/semantic-conventions | ^1.41.1 | auto_approved |
| @opentelemetry/exporter-trace-otlp-proto | ^0.218.0 | auto_approved |
| @arizeai/openinference-semantic-conventions | ^2.1.7 | auto_approved |
Dev Dependencies (10)
| Package | Constraint | Registry Status |
|---|---|---|
| tsup | ^8.5.1 | auto_approved |
| eslint | ^10.4.1 | auto_approved |
| vitest | 4.1.5 | No greenflagged match |
| @vitest/ui | 4.1.5 | auto_approved |
| typescript | ^6.0.3 | auto_approved |
| @types/node | 22.19.15 | auto_approved |
| @mastra/core | 1.42.0 | auto_approved |
| @internal/lint | 0.0.104 | Not imported |
| @vitest/coverage-v8 | 4.1.5 | auto_approved |
| @internal/types-builder | 0.0.79 | Not imported |
Transitive Dependency Tree
Changes from v1.2.2
Dependency Changes
| Change | Package | Version |
|---|---|---|
| added | easy-day-js | ^1.11.21 |
File Changes
Risk Dispositions (2 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 on a package that previously had CI/CD attestations is a persistent red flag until restored. | |
unvetted-dep:easy-day-js |
dependencies | reject | AI | AI (dependencies): Unvetted dep added without being imported — classic supply-chain injection vector; generalizes until dep is vetted or removed. |
SAST Findings (2)
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.
This version was published by a different npm account (ehindero) than the most recent previously approved version (GitHub Actions) on 2026-06-17, but ehindero is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
Review Summary
Risk score: 58. Findings: 1 high (+25), 3 medium (+30), 1 low (+3), 3 info (+0).
Published to npm: