electric-yjs
Audited by Socket on Mar 7, 2026
1 alert found:
Obfuscated FileThe skill's footprint largely aligns with its stated purpose of enabling Yjs-based collaboration via ElectricProvider with Postgres-backed persistence and resume-state management. The primary security concern is the lack of explicit authentication/authorization details for the exposed API endpoints, which could enable unauthorized data writes if not mitigated by surrounding infrastructure. Other risks are typical for collaborative systems (data at rest in BYTEA, client-side resume state exposure) and are manageable with standard security controls (auth, TLS, access controls, retention policies, and secure resume state handling). Overall, the scope is coherent and the risk is manageable with proper deployment safeguards; currently labeled as MEDIUM risk with notable suspicious signals around unauthenticated endpoints that should be addressed before production.