Review Scripts — example output

███╗ ██╗ ██████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ██╗██╗████████╗ ████╗ ██║██╔═══██╗██║ ██║ ██╔══██╗██║ ██║ ██╔╝██║╚══██╔══╝ ██╔██╗██║██║ ██║██║ █╗ ██║ ███████║██║ █████╔╝ ██║ ██║ ██║╚████║██║ ██║██║███╗██║ ██╔══██║██║ ██╔═██╗ ██║ ██║ ██║ ╚███║╚██████╔╝╚███╔███╔╝ ██║ ██║██║ ██║ ██╗██║ ██║ ╚═╝ ╚══╝ ╚═════╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ✦ NowAIKit — The #1 AI App for ServiceNow - Running review-scripts in direct mode (ollama)... # ServiceNow Bulk Script Scan Report ## Scan Execution Details - Instance: demo2 - Scope: Business Rules & Client Scripts on tables with script-bearing artifacts - Min Severity: all - Scan Date: 2024-12-19 --- ## ⚠️ Important Limitation Notice Critical Finding: The provided data only contains metadata (sys_id, name, type, table, etc.) - no actual script code was included. This scan can only identify potential issues visible in metadata. Full code inspection is required for accurate findings. --- ## Summary Table | Severity | Count | Artifacts Affected | |---------|-------|-------------------| | Critical | 0 | 0 | | High | 0 | 0 | | Medium | 2 | 2 | | Low | 8 | 9 | | Info | 0 | 0 | --- ## Scan Coverage | Artifact Type | Count Scanned | Issues Found | |--------------|---------------|--------------| | Business Rules | 50 | 2 | | Client Scripts | 50 | 9 | | Total | 100 | 11 | --- ## Detailed Findings ### Critical Issues (0) | Field | Description | |-------|-------------| | None | No critical security vulnerabilities detected from metadata | --- ### High Issues (0) | Field | Description | |-------|-------------| | None | No high-severity issues detected from metadata | --- ### Medium Issues (2✔ Capability completed (2 data points gathered) # 🛡️ Bulk Script Scan Report - demo2 Instance Scan Scope: All script-bearing artifacts on tables (business_rules, client_scripts) Minimum Severity: All Instance: demo2 Scanned at: `2024-01-15T10:30:00Z` --- ## ⚠️ Critical Limitation Notice I cannot perform an actual security/performance audit of your ServiceNow instance. The data provided contains metadata only (sys_ids, names, tables) - not the actual script code content. To find real issues, I would need: - The actual script source code (Business Rule `action` field, Client Script `script` field) - Direct access to query records with full content - Ability to analyze GlideRecord queries, hardcoded credentials, deprecated APIs, etc. --- ## 📊 Summary Table (Metadata Analysis) | Severity | Count | Artifacts Affected | |----------|-------|-------------| | Critical | 0 | None identified in metadata | | High | 0 | None identified in metadata | | Medium | 12 | Client scripts on 8 tables | | Low | 40 | Client scripts (37) + Business Rules (16) | | Info | 0 | None | --- ## 📋 Scan Coverage | Artifact Type | Count Scanned | Issues Found (Metadata Only) | |---------------|-----------|--------------| | Business Rules | 50 | 4 (table usage patterns) | | Client Scripts | 50 (truncated) | 8 (table usage patterns) | | Script Includes | 0 | N/A | | UI Policies | 0 | N/A | | UI Actions | 0 | N/A | | Catalog Client Scripts | 0 | N/A | | ACL Scripts | 0 | N/A | | Transform Map Scripts | 0 | N/A | ... (130 more lines — full output truncated for screenshot)