sf-i-events@1.0.1168
Superflows Navigation Component
AI Security Review
scanned 4d ago · by lpm-firewall-aiSource inspection found no install hook or concrete malicious behavior. The suspicious artifact signal resolves to a normal DOCX template, and the authenticated calendar request is tied to a user interface action and selected project.
Decision evidence
public snapshot- package.json identifies a browser navigation component and points to sf-i-events.js; its scripts do not define an install lifecycle hook.
- sf-i-events.js imports Lit and defines the component's runtime behavior.
- The fixed calendar API request is initiated by a calendar button click and sends the selected project ID with the application's email and access-token cookies.
- The inspected DOCX analysis identifies a standard DOCX/OPC ZIP template with no inspection limitations.
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.1168.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1168 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.