@mastra/loggers@1.3.9
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected network behavior belongs to configurable logging transports, and the main logger uses configured transports. The manifest shows no install lifecycle hook, and the inspected dependencies serve as logging and formatting components.
Decision evidence
public snapshot- The manifest exposes separate logger entrypoints and declares pino and pino-pretty as runtime dependencies.
- The package lifecycle scripts shown in the manifest are build, watch, test, and lint commands; no install hook is declared.
- The main logger passes caller options and configured transports to Pino.
- The HTTP transport sends buffered logs to its configured URL, with caller-provided method and headers.
- The Upstash transport sends buffered logs to its configured URL using its supplied token.
- The inspected dependency entrypoints identify pino as a logger and pino-pretty as a log formatter.
Source & flagged code
8 flagged · loading sourceThe manifest exposes separate logger entrypoints and declares pino and pino-pretty as runtime dependencies.
package.jsonView on unpkg · L48The package lifecycle scripts shown in the manifest are build, watch, test, and lint commands; no install hook is declared.
package.jsonView on unpkg · L83Findings
Affected versions and remediation
This report applies to @mastra/loggers@1.3.9.
See all versions of @mastra/loggers for other recorded verdicts.
- Review the evidence and your use of @mastra/loggers@1.3.9 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.