sf-i-events@1.0.1162
Superflows Navigation Component
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe component sends session credentials to a publisher-selected endpoint during an admin action, but the source does not establish whether that endpoint is a trusted service backend. Warn for conditional credential exposure; the evidence does not support blocking.
Decision evidence
public snapshot- The package entrypoint is sf-i-events.js. The manifest shows no install hook.
- An admin interface click invokes the calendar request.
- The request sends project data and Basic authorization built from the email and access-token cookies to a fixed AWS Lambda URL.
- The shared request helper places supplied authorization in an HTTP Authorization header.
- Other mapped-calendar requests use the configured API host, leaving the fixed Lambda endpoint’s relationship to that service unclear.
- The Lambda request is behind an admin interface click, not package installation or import.
- The inspected source does not establish whether the Lambda endpoint is a trusted backend for this application or whether the credentials are misused.
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.1162.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1162 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.