sf-i-events@1.0.1161
Superflows Navigation Component
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe fixed calendar endpoint receives cookie-derived credentials, while the usual event API uses a configured host, leaving destination safety unresolved. This supports a warning for conditional credential exposure, not a block; the binary required template also cannot support a clean citation.
Decision evidence
public snapshot- The calendar request sends email and accessToken cookie values as authorization to a fixed Lambda URL.
- That request is activated by a calendar mapping button click; its destination is distinct from the configured event API host.
- The required DOCX is binary and could not be resolved as UTF-8 source evidence.
- The usual event details request sends authorization to the configured API host.
- No install lifecycle scripts are declared in the inspected package manifest.
Source & flagged code
6 flagged · loading sourcePackage ships high-entropy non-source blobs.
dev/templates/table-template.docxView on unpkgPackage ships compressed or archive-like blobs.
dev/templates/table-template.docxView on unpkgPackage ships a nested archive or MCP bundle that was inventoried but not recursively analyzed.
dev/templates/table-template.docxView on unpkgFindings
Affected versions and remediation
This report applies to sf-i-events@1.0.1161.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1161 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.