Skip to main content

Limitations & Caveats

info

The English user guide is currently in beta preview. Most of the documents have been automatically translated from the Japanese version. Should you find any inaccuracies, please reach out to Flatt Security.

warning

This page does not exhaustively cover all limitations and caveats of Takumi Agent for Endpoint. Detailed disclosure of the boundaries of defense mechanisms could be exploited to circumvent them, so the content here is intentionally limited.

Takumi Agent sends installs through Takumi Guard, so Takumi Guard's limitations, such as its blocking coverage and rate limits, apply as well. This page covers the limits of the agent itself.

Supported Platforms​

Takumi Agent runs only on Apple silicon Macs with macOS 13 (Ventura) or later. Intel Macs, Linux, Windows and CI are not supported. Use the registry setup on those machines.

Traffic Outside the Supported Registries​

Takumi Agent captures only the registries listed under What is covered. A tool pointed at any other host, such as a private registry, another mirror or a proxy outside the Mac, never talks to those registries, so its traffic doesn't go through Takumi Guard. The same applies to Git and tarball URLs and to Go modules fetched straight from version control (GOPROXY=direct, GOPRIVATE). Restricting those hosts is a job for your network's egress policy.

Private Packages on Public Registries​

Installing a private package hosted on a public package registry, such as a private package on registry.npmjs.org, doesn't work on a Mac with Takumi Agent. The install reaches Guard with your organization's token instead of yours, so the registry refuses it. Install those packages from CI, or host them on a private registry. See Registry credentials and publishing.

When Takumi Guard Can't Be Reached​

Installs from the supported registries fail while Takumi Guard can't be reached, and there is no way around it on the Mac. Nothing is installed unchecked.

The Device Certificate​

Every runtime that downloads from a supported registry must trust the Mac's device certificate. Takumi Agent sets up the common tools on the Mac for you, but tools that don't use the macOS keychain need their own setting, and every container or VM has its own trust store that needs a one-time setup per developer. Until then, installs inside it are blocked, not let through. Developing with Takumi Agent covers each case.

Rate Limits​

Devices with Takumi Agent get the same rate limit as Takumi Guard org user tokens: 10,000 requests per 10 seconds per device. A device token and an org user token count against the same kind of per-token bucket: 10,000 requests per 10 seconds, all ecosystems together.

info

The rate limit applies only to requests to the registries that Guard protection covers.

Requests over the limit are rejected with 429 Too Many Requests.

See Rate Limits for details.