@meetelise/chat@1.53.0
### Installation
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe install and developer scripts show ordinary package sorting, hook setup, build, and interactive release workflow. The inspected runtime request sends the page URL to the package-aligned service for a building lookup; no concrete attack surface was established.
Decision evidence
public snapshot- package.json defines postinstall as sort-package-json, prepare as husky install, and prepublishOnly as a build; none installs a runtime release of this package or expands consumer script approvals.
- The runtime sends the current page URL to app.meetelise.com to look up a building slug, using the configured organization slug as a request header.
- The flagged deploy.sh helper asks the developer to choose a version bump and confirm before pushing.
- No concrete attack behavior was identified in the inspected package sources.
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.53.0.
See all versions of @meetelise/chat for other recorded verdicts.
- Review the evidence and your use of @meetelise/chat@1.53.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.