@meetelise/chat@1.52.0
### Installation
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe inspected lifecycle hooks are conventional package maintenance commands, and the runtime network calls are directed to the package vendor’s API for chat lookup and analytics. The observed dynamic-code match in the bundle is an ECMAScript intrinsic reference, not evidence of an active execution path.
Decision evidence
public snapshot- The postinstall hook sorts package metadata, prepare installs the project’s Husky hooks, and prepublishOnly runs the build.
- Analytics sends events to MeetElise’s API with browser credentials omitted.
- The building lookup sends the current page URL to MeetElise’s API when the package handles a single-family URL.
- Analytics gathers campaign values from the current page URL and a named campaign cookie.
Source & flagged code
4 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
public/dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @meetelise/chat@1.52.0.
See all versions of @meetelise/chat for other recorded verdicts.
- Review the evidence and your use of @meetelise/chat@1.52.0 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.