sf-i-events@1.0.1158
Superflows Navigation Component
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe calendar request forwards cookie-derived credentials to a fixed endpoint whose relationship to the package's service is not established by inspected source. This is an unresolved credential exposure risk, so warn without blocking.
Decision evidence
public snapshot- src/sf-i-events.ts sends the email and access token read from cookies to a hardcoded AWS Lambda URL when fetchCalendar runs.
- src/util.ts posts requests to the supplied URL and places the supplied authorization value in the Authorization header.
- The endpoint appears in a calendar scheduling feature, but source inspection does not establish that it is the intended service or who controls it.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The package is a browser component whose calendar API calls are tied to user-facing feature methods.
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.1158.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1158 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.