We are rolling out AI Penetration Testing to pre-registered customers more broadly than before.
We have also improved how accurately Takumi finds the paths that lead to a given objective, along with the safeguards that keep a test running safely.
Bot trust conditions now accept ID tokens from any identity provider that complies with OIDC Discovery, not just GitHub Actions and GitLab CI.
Self-hosted CI/CD systems such as Jenkins, Buildkite, and CircleCI, another cloud's workload identity federation, GitHub Enterprise Server, and self-managed GitLab can all sign in as a bot without a static API key.
Custom OIDC provider support is currently in beta. Specifications and behavior may change without prior notice.
In Takumi blackbox assessments, APIs that have no web UI can now be specified as an assessment target.
Instead of crawling with a web browser, Takumi extracts the endpoints to assess from the attached schema files, such as an OpenAPI specification or a GraphQL schema.
We are expanding access to AI Penetration Testing, which we began rolling out on June 15, 2026, to more customers. The feature verifies whether a given objective is achievable, from the perspective of a real attacker.
Set a target and a concrete objective — such as accessing user data — and Takumi autonomously chains reconnaissance, vulnerability discovery, and exploitation.
The feature is not yet available to all customers, so if you'd like to use it, register from the application page.
Takumi Images is now available in beta. It provides maintained container images that are continuously rebuilt and scanned so your applications can start from base images where known vulnerabilities have already been addressed.
The images are published through the OCI registry images.flatt.tech.
Takumi Runner now lets you search the trace data it has collected over a date range you specify. Previously you could only search the trace data of a single job, but with this search feature you can detect suspicious activity across every job within a given period.
This page also walks through how to use the search feature with real-world examples, such as the axios supply chain attack in March 2026. See Examples below.
The Takumi Guard log viewer has been rebuilt as a single, unified Log Browser that replaces the previous log search page. Search a package, browse recent activity across your organization, group installs by repository, workflow, or user, and share a link to exactly what you are looking at.
Takumi Guard admin deployment now configures Packagist — the PHP/Composer ecosystem — on every target machine, alongside npm, PyPI, RubyGems, and Go modules.
Takumi Guard's setup script (setup.sh / setup.ps1) now includes a healthcheck subcommand that verifies Guard is correctly configured and actively blocking malicious packages — all without modifying any files or requiring API credentials.
Takumi Guard now rewrites tarball download URLs for npm v11.15.0 and later, keeping installs working with npm's new supply chain protections. Users on these npm versions will see Takumi Guard's registry URL in their package-lock.json files.