beUI Pro

Use the customer's licensed beUI Pro registry as the source of truth. Discover current items at runtime, install only the blocks the project needs, then compose and adapt the generated source.

Protect access

• Require BEUI_PRO_TOKEN in the environment before accessing the registry.
• Never print, paste, commit, or write the token into source files.
• Never accept a token copied into the user's prompt when an environment variable can be used.
• Stop and ask the user to configure their token when it is unavailable. Do not replace a requested Pro block with an approximation.
• If the live catalog cannot be fetched, do not present remembered, documented, or locally inferred slugs as the current catalog.
• Treat 401 as a missing, invalid, or expired token. Treat 404 as a stale or incorrect install slug and refresh the catalog.

Check access without revealing the value:

test -n "$BEUI_PRO_TOKEN" && echo "beUI Pro token is configured"