@mastra/qdrant@1.1.5
Qdrant vector store provider for Mastra
AI Security Review
scanned 2d ago · by lpm-firewall-aiInspected entrypoints and the required dependency source show ordinary Qdrant client behavior and no package install hook or unrelated collection or transfer. The request destination is configured by the caller through Qdrant client parameters.
Decision evidence
public snapshot- package.json exposes the library entrypoints and declares the Qdrant REST client dependency; its scripts show no install lifecycle hook.
- The package passes caller-provided Qdrant parameters to the Qdrant client when a vector store is constructed.
- The dependency entrypoints re-export QdrantClient, and its request code builds URLs from the client base URL and sends requests through fetch.
- The dependency manifest declares no lifecycle scripts in the inspected manifest; its browser entrypoint implements ordinary HTTP request handling.
Source & flagged code
8 flagged · loading sourcepackage.json exposes the library entrypoints and declares the Qdrant REST client dependency; its scripts show no install lifecycle hook.
package.jsonView on unpkg · L22package.json exposes the library entrypoints and declares the Qdrant REST client dependency; its scripts show no install lifecycle hook.
package.jsonView on unpkg · L56Findings
Affected versions and remediation
This report applies to @mastra/qdrant@1.1.5.
See all versions of @mastra/qdrant for other recorded verdicts.
- Review the evidence and your use of @mastra/qdrant@1.1.5 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.