igrantio-individuals

Pass

Audited by Gen Agent Trust Hub on Jul 20, 2026

Risk Level: SAFE
Full Analysis
  • [EXTERNAL_DOWNLOADS]: The skill makes network requests to official iGrant.io API domains (demo-api.igrant.io and staging-api.igrant.io) to manage individual user profiles and consent records. This is standard behavior for an integration client and aligns with the vendor's provided services.\n- [CREDENTIALS_UNSAFE]: Sensitive organization API keys are handled using environment variables (OWS_API_KEY), which is the recommended method for secret management. The documentation correctly emphasizes that these credentials must only be used in server-side environments and never exposed to the client-side.\n- [COMMAND_EXECUTION]: The package configuration includes scripts for local development and starting the server using tsx. These are standard development tools and do not involve arbitrary or malicious command execution patterns.\n- [SAFE]: The reference server implementation uses a simplified authentication check via a custom request header for demonstration purposes. The code and accompanying documentation explicitly instruct developers to replace this with a robust authentication system, such as JWT, in production environments.
Audit Metadata
Risk Level
SAFE
Analyzed
Jul 20, 2026, 02:05 PM
Security Audit — agent-trust-hub — igrantio-individuals