@tanay-wispr/webflow-package@6.7.10
Developer starter template for Finsweet projects.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe critical scanner findings describe browser-side, user-invoked product flows rather than covert package behavior. There is no lifecycle hook or confirmed install-time attack path.
Decision evidence
public snapshot- The Android wait-list browser script posts a user-entered phone number only to the Wispr API with an authorization token.
- The downloads browser script sends app-download analytics, including optional user and marketing identifiers, to the Wispr API.
- The manifest distributes browser artifacts and has no preinstall, install, or postinstall hook.
- The observed requests are tied to visible authentication, wait-list, download, and analytics flows.
- No install-time execution, shell/process execution, local file harvesting, or remote payload loading was found.
Source & flagged code
7 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/androidWaitlist.jsView on unpkgFindings
Affected versions and remediation
This report applies to @tanay-wispr/webflow-package@6.7.10.
See all versions of @tanay-wispr/webflow-package for other recorded verdicts.
- Review the evidence and your use of @tanay-wispr/webflow-package@6.7.10 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.