0.5.1 - Growing Strong

New Features

• Added database performance tooling for generating large Case, Alert, Artifact, Enrichment, Playbook, Knowledge, and AuditLog datasets, plus ORM/API hotspot benchmarks.
• Added AuditLog management settings so retention, cleanup, and cascade delete logging can be adjusted per deployment.
• Registered the asp-marketplace submodule as the independent code entry point for future Claude Code plugin distribution and maintenance.

Improvements

• Greatly improved Dashboard query paths for large datasets by pushing top-risk artifacts, threat keywords, mean times, and active risk index aggregation to the database.
• Improved default Case, Alert, and Artifact list performance with time-order indexes and by avoiding expensive related-count aggregation on default requests.
• Web detail payloads for Case, Alert, and Artifact are now lightweight; Case Investigation is loaded through a dedicated lazy endpoint instead of serializing large related trees up front.
• All readable_id models now use PostgreSQL sequences for identifier generation, avoiding large-table max scans on writes and improving concurrent write stability.
• Table tag rendering now shows the first two tags plus the remaining count, removing per-cell measurement and ResizeObserver usage from large tables.
• Added operation timeouts for external requests to reduce the risk of third-party services stalling background work.
• Production deployment settings now include Gunicorn gthread tuning, Nginx upstream keepalive/gzip, PostgreSQL runtime tuning, and Django database connection controls.
• Frontend build and development dependencies were upgraded to Vite 8.1.3, @vitejs/plugin-react 6.0.3, typescript-eslint 8.63.0, globals 17.7.0, and lucide-react 1.23.0.

Fixes

• Fixed the Mock Case TTD calculation issue.
• Fixed incomplete audit logging for cascade deletes.
• Reverted the higher-maintenance raw SQL Dashboard summary optimization and kept the lower-risk aggregation improvements that provided clearer value.
• Fixed CodeQL exception exposure findings: Webhooks, configuration tests, custom definition scans, Agent API calls, Playbook failure remarks, Threat Intelligence queries, and CMDB lookups now log detailed exceptions server-side while returning safe generic API errors.
• Fixed a potential ReDoS risk in OpenCTI STIX pattern matching by replacing the high-risk regular expression with a linear parser.
• Fixed the frontend CI hooks lint issue in the lazy Case Investigation component.

Deployment and Release Engineering

• Release configuration continues to use deploy/release-manifest.json as the source of truth, with deploy/release_tool.py generating CLI version, Compose examples, quick-start docs, release pages, and VitePress nav.
• The Compose release package now defaults to 0.5.1 image tags while keeping production Gunicorn, PostgreSQL, and database connection parameters configurable.
• Release workflow, runbook, and managed-file generation were further standardized to reduce manual edits for patch releases.
• CI, Docker, and Release dependencies were upgraded to actions/setup-python 6, actions/setup-node 6, docker/setup-buildx-action 4, docker/build-push-action 7, and softprops/action-gh-release 3.
• The frontend production image now uses nginx:1.31-alpine.

Upgrade Notes

If you already deployed 0.5.0, back up first, then update image versions in .env:

ASP_BACKEND_IMAGE=ghcr.io/funnywolf/agentic-soc-platform/asp-backend:0.5.1
ASP_FRONTEND_IMAGE=ghcr.io/funnywolf/agentic-soc-platform/asp-frontend:0.5.1

Run the upgrade:

./scripts/upgrade.sh

This release includes database migrations that create new time-order indexes and readable_id sequences. Instances with large datasets may take longer to migrate, so plan a maintenance window.

If you maintain a customized .env, compare it with the updated deploy/asp-compose/.env.example and merge the new Gunicorn, PostgreSQL, and database connection parameters as needed.

Related-count columns still display counts, but sorting by those counts is no longer available. This avoids full-table grouping and sorting on million-row datasets.

Some configuration test and Webhook failure responses now return more generic error messages. Detailed exceptions are still written to server logs, but are no longer exposed directly to API callers.

To use the CLI:

pipx install asp-cli==0.5.1

If asp-cli is already installed, upgrade to the latest version:

pipx upgrade asp-cli

You can also force-install a specific version:

pipx install asp-cli==0.5.1 --force

Developer Notes

The title of this release borrows the Tyrell house words: Growing Strong.

0.5.1 is less about adding visible surface area and more about making the platform stay strong as data grows. The performance tooling created extreme datasets first, then used the actual slow paths to drive the work: Dashboard aggregation, default lists, detail payloads, frontend table rendering, production deployment settings, and write-path identifier generation all converge on the same goal.

This release also clears the exception exposure issues reported by CodeQL. The tradeoff is straightforward: logs can keep the details, but API responses should not hand internal exceptions, paths, SDK errors, or upstream diagnostics directly to callers.

A system grows stronger not by assuming the data will stay small, and not by assuming errors are only seen by trusted users, but by staying clear, measurable, and maintainable when the data becomes large and failures actually happen.