All @mastra/auth-cloud versions
@mastra/auth-cloud @1.1.4
Mastra Cloud authentication with PKCE OAuth
Maintainers
Dependencies (2)
| Package | Constraint | Registry Status |
|---|---|---|
| easy-day-js | ^1.11.21 | auto_approved |
| @mastra/auth | 1.0.2 | auto_approved |
Dev Dependencies (10)
| Package | Constraint | Registry Status |
|---|---|---|
| tsup | ^8.5.1 | auto_approved |
| eslint | ^10.2.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.39.0 | auto_approved |
| @internal/lint | 0.0.101 | Not imported |
| @vitest/coverage-v8 | 4.1.5 | auto_approved |
| @internal/types-builder | 0.0.76 | Not imported |
Transitive Dependency Tree
Changes from v1.1.3
Dependency Changes
| Change | Package | Version |
|---|---|---|
| added | easy-day-js | ^1.11.21 |
File Changes
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): Prior versions had CI/CD provenance attestations; manual publish without attestation is a strong compromise signal for this package. |
SAST Findings (3)
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.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ehindero.
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), 4 info (+0).
Published to npm: