oracle-apex-object-lock
Pass
Audited by Gen Agent Trust Hub on Aug 10, 2026
Risk Level: SAFECOMMAND_EXECUTIONPROMPT_INJECTION
Full Analysis
- [SAFE]: The skill provides database management scripts for coordinating changes in a shared Oracle environment. It uses standard PL/SQL practices, including bind variables and identifier validation (dbms_assert.simple_sql_name), to ensure safe operation.\n- [COMMAND_EXECUTION]: The skill requires the agent to execute SQL scripts (audit-installation.sql, install.sql) via SQLcl. These operations are scoped to the project's database environment and are documented as necessary steps for establishing the cooperative lock runtime.\n- [PROMPT_INJECTION]: Ingestion points: audit-installation.sql and validate-installation.sql process metadata from USER_OBJECTS. Capability inventory: SQL execution through SQLcl for auditing and installation. Sanitization: The installation script uses dbms_assert.simple_sql_name for dynamic identifier construction, and the PL/SQL package body employs name normalization (upper/replace/trim) for object names. Boundary markers are absent in the auditing logic, but the risk is low given the intended developer-centric use case.
Audit Metadata