sf-i-events@1.0.1170
Superflows Navigation Component
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe entrypoint has no install hook, and the inspected credential use is tied to the component’s calendar request. Static alerts point to a normal calendar service call, a declared fs dependency without observed source use, and an inert reporting template.
Decision evidence
public snapshot- package.json identifies sf-i-events.js as the module entrypoint and contains no install lifecycle hook.
- The bundled calendar feature posts the selected project’s calendar request to its calendar service.
- The calendar request uses the app’s email and access token as authentication; the shared helper sends them in an Authorization header with the POST.
- The bundled component calls the calendar fetch when the user returns from calendar mapping.
- The inspected document is a DOCX reporting template with no analysis limitations; it is inert data in the reviewed source.
- package.json declares an fs dependency, but the inspected source does not use it; this matches a static name-based dependency alert rather than observed behavior.
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.1170.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1170 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.