sf-i-events@1.0.1173
⚠ Under reviewSuperflows Navigation Component
AI Security Review
scanned 2d ago · by lpm-firewall-aiManual review is warranted because the entrypoint imports chart.js, whose prepared source could not be resolved, and sends cookie-derived credentials to a fixed endpoint whose product alignment is unknown. The source confirms a user-triggered calendar request but does not establish malicious transfer.
Decision evidence
public snapshot- package.json selects sf-i-events.js as the entrypoint; that file imports chart.js, which is declared as a dependency.
- The calendar request reads email and accessToken cookies and sends an encoded authorization value to a fixed AWS Lambda URL; the recipient’s relationship to the product is unverified.
- The manifest has no install lifecycle hook, and the calendar request is called from a component button handler.
- The inspected source does not establish that the Lambda endpoint is unrelated to the package’s service.
- No install-time or post-install behavior was identified in package.json.
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.1173.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1173 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.