@mastra/auth-clerk@1.3.1
⚠ Under reviewMastra Clerk Auth integration
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected source implements Clerk authentication and showed no concrete attack behavior. The declared @clerk/backend dependency is used at runtime but its source was unavailable in the prepared snapshot, so the review remains unresolved.
Decision evidence
public snapshot- The manifest declares no install lifecycle hook and imports the built library from its published entrypoints.
- The provider uses configured Clerk credentials and the Clerk client; its OAuth token exchange goes to a URL derived from the Clerk publishable key.
- The declared Clerk backend dependency is imported and used, but its implementation is absent from the inspected snapshot, leaving its behavior unresolved.
- Inspected code showed no credential transfer to an unrelated recipient or automatic account changes.
- The prepared @mastra/auth dependency verifies JWTs using the configured JWKS URI.
Source & flagged code
8 flagged · loading sourceA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.cjs#virtual:normalized:round1View on unpkgThe manifest declares no install lifecycle hook and imports the built library from its published entrypoints.
package.jsonView on unpkg · L52Findings
Affected versions and remediation
This report applies to @mastra/auth-clerk@1.3.1.
See all versions of @mastra/auth-clerk for other recorded verdicts.
- Review the evidence and your use of @mastra/auth-clerk@1.3.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.