Home
The AISafe changelog tracks notable customer-facing platform and documentation updates. Each version marks the shape of the product at that point in its development, and each release lists the changes that users can act on.
v2 (current)
Reorganized the documentation and public site.
- Changed
POST /api/v1/assessments/{id}/revisions,/revisions/uploadand/revisions/patch: each now answers202with an attachment to poll instead of the revision, and accepts anidempotency_key. A failed attempt needs a new key. See Updating source through the API. - Changed
POST /api/v1/projects/{id}/revisionsand/revisions/uploadthe same way, and addedPOST /api/v1/projects/{id}/revisions/patch, which applies a unified diff to a project revision. PollGET /api/v1/projects/{id}/revision-attachments/{attachment_id}. See Updating project source through the API. - Removed
target_pathfrom project uploads (/revisions/upload, the resumable upload'sproject_revisiontarget andaisafe upload --target-path). An uploaded archive is always the project's whole codebase, and a project connected to repositories refuses uploads withproject_source_is_repositorybecause its changes come from those repositories. See Updating project source through the API. - Rebuilt Black-Box Pentest on the current assessment engine. Each confirmed finding now points to captured HTTP request/response evidence, and every planned test ends with a covered or uncovered result in the run record.
- Restructured the docs into Home, Services, Platform, and Changelog.
- Added a Services section with one category per service: Source Code Audit, White-Box Pentest, Black-Box Pentest, Endpoint Monitoring, and Pull Request Review. Each category covers how the service works, how to set it up, and how to read its findings.
- Reworked Concepts into one page per core noun, from your Account through Organization, Project, Assessment, Finding, Report, and Credits.
- Kept the dashboard on the Home page: ask how to run a service, browse the services, and explore the platform from one screen.
v1
The original public documentation.
- Introduced the Home, Services, Platform, and Changelog tabs.
- Documented the flat set of features: code audit, pentest, PR review, scheduled scans, monitoring, triage, and reports — each as a single page under Platform.
- Listed REST API conventions, authentication, errors, and webhooks, with a generated per-endpoint reference.
- Provided getting-started flows: create an account, run your first assessment, invite your team, and a dashboard overview.
In the move to v2, the flat feature pages became the five standalone Services, scheduled scans and monitoring merged into Endpoint Monitoring, and the public API reference pages were retired from the customer docs.