sf-i-events@1.0.1164
Superflows Navigation Component
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found a browser component and a user-triggered, authenticated calendar request whose host is listed in the package demo configuration. The flagged DOCX is a normal report template, and no concrete malicious behavior was established.
Decision evidence
public snapshot- The manifest identifies sf-i-events.js as the package entrypoint and declares it as an ES module.
- The bundled component’s DOCX template is a regular Word document with document XML; the offline analysis reports no inspection limitations.
- The calendar request sends the selected project ID with the app’s email and access token to the calendar scheduling endpoint.
- The request is triggered by clicking the Back Calendar Mapping control, and the demo config lists the same host as apiid2.
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.1164.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1164 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.