@webtwizz/cloud
Sign-ins, database and file storage for sites built on WebTwizz Cloud
This report shows the evidence for @webtwizz/cloud@0.5.1. 0 of 6 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no install hook that performs network activity, and its exported features direct requests to configured service endpoints. The network and credential handling inspected matches the package's stated purpose; no malicious behavior was found.
Decision evidence
public snapshot- The package exports auth, database, storage, and email helpers consistent with its stated purpose.
- The only lifecycle script is prepublishOnly, which runs build, typecheck, and tests.
- Auth requests use the supplied URL or WEBTWIZZ_AUTH_URL; session cookies are forwarded to that configured upstream.
- Storage uses configured endpoint and credentials for S3 operations.
- No install-time hook or automatic data collection was identified.
- The code contains network requests for its advertised authentication, email verification, database, and file-storage features.
- Auth, storage, and database destinations are supplied through package options or environment configuration rather than unrelated hard-coded hosts.
Source & flagged code
6 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
AI_GUIDE.mdView on unpkgThe package exports auth, database, storage, and email helpers consistent with its stated purpose.
package.jsonView on unpkg · L21Findings
Affected versions and remediation
This report applies to @webtwizz/cloud@0.5.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @webtwizz/cloud@0.5.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.