Aiholey

Lazy cat OIDC login has been integrated. Note: It is recommended to use it in conjunction with Piggy Page to facilitate accessing the GitHub project warehouse. ##Functional characteristics - Manage Git repository addresses, branches, tokens or SSH keys, test connections and pull working copies. - Create manual, interval, cron, or single Code Audit tasks to view queues, progress, phases, and real-time logs. - Use built-in rules to discover issues such as credential leakage, injection, deserialization, and path crossing; add AI semantic analysis after configuring compatible interfaces. - Manage built-in audit skill prompts and support starting and stopping, editing, adding and restoring default skills. - Quickly scan pulled warehouses or directories in containers without creating tasks. - Perform port discovery, service identification and read-only Web security detection on authorized sites, and support three depths of quick / standard / deep. - View reports by level, category, skill, and warehouse; export HTML, Markdown, JSON, and HTML can be printed as PDF. - The dashboard summarizes vulnerability levels, recent 7-day trends, classification distribution, and warehouse risk rankings. ###First use process 1. Open the app and log in using your lazy cat account. 2. You can also use the rules engine first without configuring the model. Go to "Warehouse Management" → "New Warehouse", create a 'Chinese example warehouse', fill in a Github address and branch that you have the right to audit, click Test Connect and pull it. 3. Enter "Audit Tasks" → "New Tasks", fill in the name of 'September Code Security Review', select warehouse,'Standard (Standard Audit)', required skills and manual scheduling, save and click Run. 4. In the operation record, you can see that the status has moved from queuing to execution. After completion, open the report to confirm that there are level statistics and problem lists; a complete report should also be generated if no items are found. Note: If pulling the warehouse or executing the task is not successful, you can try again or check whether the network is connected using Piggy Page. ###Daily usage | Warehouse maintenance| Add, edit, test connection, pull or deactivate warehouses in "Warehouse Management"; fill in only the warehouses you have the right to access| | Tasks and Scheduling| Select depth, engine, skills and manual/interval/cron/single schedule in "Audit Task"; view real-time progress in "Execution Engine" and stop as needed| | fast scan| Select the allowed directories in the pulled warehouse or container in "Quick Scan", and you can execute it without creating a long-term task| | Report review| Filter by warehouse, status and level in the "Audit Report", open vulnerability details, suggestions and source code locations, and initiate a re-scan if necessary| | report export| Download HTML/Markdown/JSON or batch Markdown; choose local file system or lazy cat microservice, HTML can be printed as PDF in browser| | Web missed scan| Fill in URL/IP only for explicitly authorized targets, first use Quick; to view ports, evidence and suggestions, and then increase the depth after confirming the scope| | Skill Maintenance| Start and stop or edit prompts in the "Skill Library"; keep a copy before modifying, and use the "Restore Built-in Prompt" to return to the default set| Q: Can I use it without configuring a large model API Key? A: Yes. When not configured, it is automatically downgraded to pure built-in rule scanning: 22 audit regular patterns + 27 Web read-only probes work as usual, and reports are produced as usual. After configuring the Key, you will gain additional AI project adaptation, semantic analysis and autonomous penetration planning.