sf-i-events@1.0.1159
⚠ Under reviewSuperflows Navigation Component
AI Security Review
scanned 15d ago · by lpm-firewall-aiInspection found no install-time execution or confirmed malicious behavior. The required high-finding DOCX artifact could not be inspected or cited, so clean citation coverage is incomplete and the package requires manual review.
Decision evidence
public snapshot- package.json has no install lifecycle hooks; its scripts are development and test commands.
- sf-i-events.js sends the project calendar request to a fixed AWS Lambda endpoint and constructs authorization from email and access-token cookies.
- util.js posts requests and adds the supplied authorization header when present.
- The required DOCX artifact could not be inspected or cited because the source tool rejected binary content; clean citation coverage is incomplete.
- The package is a browser component, and the calendar request is part of its project data flow.
- The manifest contains no install lifecycle hook.
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.1159.
See all versions of sf-i-events for other recorded verdicts.
- Review the evidence and your use of sf-i-events@1.0.1159 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.