@tanay-wispr/webflow-package@6.6.14
Developer starter template for Finsweet projects.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection shows a Webflow/browser integration package whose suspicious primitives are aligned with its advertised Wispr Flow website functionality. There is no install-time execution, host-level capability, credential harvesting beyond expected browser auth/session handling, or unaligned exfiltration endpoint.
Decision evidence
public snapshot- package.json has no install/preinstall/postinstall/prepare lifecycle hooks.
- Published files are bundled browser/Webflow scripts under dist/, activated by page inclusion/user interaction.
- Network calls are product-aligned to api.wisprflow.ai and dodjkfqhwrzqjwkfnthl.supabase.co for signup, auth, pricing, downloads, and demo transcription.
- dist/downloads.js critical-looking secret is a Supabase anon JWT embedded with supabase-js client config, not a private service key by itself.
- No child_process, filesystem writes, shell execution, eval/new Function, native binary loading, persistence, or AI-agent control-surface writes found.
- Audio capture in dist/web-demo/index.js uses browser getUserMedia and sends to Wispr Flow demo APIs after page/demo interaction.
Source & flagged code
15 flaggedPackage contains a critical-looking secret pattern.
dist/downloads.jsView on unpkg · L1Supabase service role key (JWT) in dist/downloads.js
dist/downloads.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @tanay-wispr/webflow-package@6.6.14.
See all versions of @tanay-wispr/webflow-package for other recorded verdicts.
- Review the evidence and your use of @tanay-wispr/webflow-package@6.6.14 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.