菜单
Commands for loading and managing scan data — ingesting federal domains, enqueueing scans, running single-site tests, and exporting snapshots.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Runbook for diagnosing and resolving production issues with the Site Scanning Engine on Cloud.gov.
Guide for deploying the Site Scanning Engine to Cloud.gov via GitHub Actions, and using the Cloud Foundry CLI to monitor and troubleshoot deployed environments.
Guide for adding new fields/columns to scan results, including entity decorators, snapshot integration, and API exposure.
Guide for implementing a new scan in the core-scanner library, including page evaluation, entity integration, and testing.
Common development commands and workflows — linting, testing, building, Docker management, and troubleshooting.
Guide through initial development setup of the Site Scanning Engine (prerequisites, Docker, building, first data load).
基于 SOC 职业分类
| name | load-data |
| description | Commands for loading and managing scan data — ingesting federal domains, enqueueing scans, running single-site tests, and exporting snapshots. |
Commands for working with scan data in the Site Scanning Engine.
Load websites from Federal Website Index into the database:
npm run ingest -- --limit 200
Options:
--limit N - Limit to N websites (recommended for local dev)Source: https://github.com/GSA/federal-website-index/blob/main/data/site-scanning-target-url-list.csv
Note: This is a prerequisite for all scanning operations. Must be run before enqueueing scans.
Queue all websites in database for scanning:
npx nest start cli -- enqueue-scans
This adds jobs to the Redis queue for the scan-engine workers to consume.
Test scan a single site without writing to database:
npx nest start cli -- scan-site --url 18f.gov
Use cases:
Note: Results are printed to console but not persisted to database.
Generate snapshot and export to S3:
npm run snapshot
What this does:
Note: Snapshot generation is difficult to test locally because Minio configuration is limited in local dev. If issues occur, address them in the deployed environment.
website tablecore_result table