igrantio-holder-backend
Pass
Audited by Gen Agent Trust Hub on Aug 19, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill implements a 'least privilege' proxy architecture. Sensitive OWS API keys are managed exclusively on the server side via
EnvTenantStoreand are never exposed to the client-side frontend. - [SAFE]: The backend uses a strict allow-list (
HOLDER_PERMITTED_PATHS) implemented with regular expressions to ensure the proxy only routes traffic to holder-specific endpoints, explicitly blocking issuer and verifier operations to prevent privilege escalation within the multi-tenant suite. - [SAFE]: The server implements secure SSE (Server-Sent Events) relaying in
notificationsSse.ts. It handles the limitation of the browserEventSourceAPI (inability to send custom headers) by injecting the authentication token as a query parameter only in the backend-to-upstream communication channel. - [SAFE]: Standard security headers and CORS configurations are applied in
server.ts. The CORS policy is configurable via environment variables, defaulting to reflected origins only during development, which is a common and acceptable practice for reference implementations. - [SAFE]: No hardcoded credentials were found. The implementation uses
.env.exampleto guide users on secure secret management using environment variables, which aligns with industry best practices.
Audit Metadata