@tanay-wispr/webflow-package@6.7.1
Developer starter template for Finsweet projects.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged network behavior is visible, but it is confined to a user-facing browser service flow and targets the named Wispr Flow service. There is no lifecycle execution or concrete malicious chain.
Decision evidence
public snapshot- The downloads bundle posts download analytics, including an email and advertising identifiers, to the Wispr Flow API.
- package.json has no preinstall, install, postinstall, or prepare hook.
- The observed requests implement browser sign-in, subscription, referral, waitlist, and download flows against the named service.
- The code activates through a Webflow browser callback, not during npm installation.
- No package-authored shell execution, filesystem access, native loading, or AI-agent configuration changes were found.
Source & flagged code
7 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/downloads.jsView on unpkgThe downloads bundle posts download analytics, including an email and advertising identifiers, to the Wispr Flow API.
Findings
Affected versions and remediation
This report applies to @tanay-wispr/webflow-package@6.7.1.
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.1 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.