[ralyodio]

The shared user-profile module for every Profullstack property. Signup pages collect the same six fields, in the order the sales tools import them:

email, first_name, last_name, company_domain, job_title, linkedin_url

• Validation and normalization: the company domain is derived from a work email (never from gmail, proton or relay mailboxes); any LinkedIn URL or handle becomes https://www.linkedin.com/in/<slug>; links in name fields are refused.
• Signup fields as an HTML string (Hono/static) and as a React component (/react), with the correct autocomplete tokens.
• A store on postgres.js, pg, libSQL/Turso and server-side Supabase that owns its schema via migrate(). It creates user_profiles, or adds only the missing columns to an existing profiles/users table, under a Postgres advisory lock.
• GET/PUT/PATCH /api/v1/me/profile handlers on Web Request/Response (Next route exports or mountProfileRoutes(app) on Hono).
• profile CLI (migrate, get, find, set, check, schema, export csv/tsv/json with --complete) and profile mcp (stdio, no SDK dependency).

Tests: 66, libSQL in memory plus a real Postgres service in CI.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	postgres@​3.4.9
	react@​19.3.1
	@​libsql/​client@​0.15.15
	react-dom@​19.3.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Deprecated by its maintainer: npm node-domexception Reason: Use your platform's native DOMException instead From: package-lock.json → npm/@libsql/client@0.15.15 → npm/node-domexception@1.0.0 ℹ Read more on: This package | This alert | What is a deprecated package? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-domexception@1.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report