sf-i-events@1.0.1154
Superflows Navigation Component
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource establishes forwarding of existing session credentials to an unrestricted configurable destination. The visible application workflow and absence of concrete malicious behavior support a warning rather than a publication block.
Decision evidence
public snapshot- util.js reads existing browser cookies, including the session credentials used by the component.
- sf-i-events.js combines email and accessToken cookies and forwards them to an HTTPS destination selected through the public apiId property.
- prepareXhr passes the destination and credentials directly to util.js, which sends them in a Basic Authorization header without destination validation.
- Clicking the project sync button invokes fetchList; successful processing calls fetchReprogramAdhoc and activates the credential forwarding.
- package.json selects sf-i-events.js as both runtime entrypoints.
- No npm install lifecycle hooks or runtime self-dependency were found.
- Requests implement visible project and calendar operations; no covert theft or malware intent was established.
- The document archive contains ordinary Word XML parts with no macros or executable entries.
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.1154.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1154 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.