Codewerk
compose validate
Parses the YAML (anchors and merge keys allowed) and validates it with the official compose-spec JSON Schema (draft 2020-12, compose-spec/compose-spec commit 3a4a699 of 2026-10-23, Apache-2.0, stored in daten/E07) using Ajv; errors are reported with JSON pointer paths. Service rules: memory and CPU limits (deploy.resources.limits, mem_limit, cpus), privileged, network_mode/pid/ipc/userns_mode host, docker.sock mounts, dangerous cap_add, unconfined security_opt, images without tag or :latest,.
POST https://code.halowerk.com/v1/compose-validateInputs
| Field | Type | Required | Description |
|---|---|---|---|
| compose | string | Yes | Content of compose.yaml / docker-compose.yml. |
Show full input schema
{
"type": "object",
"additionalProperties": false,
"required": [
"compose"
],
"properties": {
"compose": {
"type": "string",
"minLength": 1,
"maxLength": 1000000,
"description": "Content of compose.yaml / docker-compose.yml."
}
}
}Published input example
{
"compose": "services:\n web:\n image: nginx:1.27\n ports:\n - \"8080:80\"\n deploy:\n resources:\n limits:\n cpus: \"0.5\"\n memory: 256M\n"
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-17 UTC.
More endpoints in this hub
- Codewerk0.003 USDC
action sha pin
POSThttps://code.halowerk.com/v1/action-sha-pinFinds every "uses: owner/repo[/path]@ref" in a GitHub Actions workflow, resolves tags (including annotated tags) and branches to the commit SHA with git ls-remote against github.com, and rewrites the line to "uses: owner/repo[/path]@<sha> #
- Codewerk0.003 USDC
actionlint
POSThttps://code.halowerk.com/v1/actionlintRuns the official statically linked actionlint 1.7.12 release binary (MIT, SHA-256 checked against the published checksums) in an isolated child process without network, with the bundled ShellCheck 0.11.0 for run: scripts (pyflakes is not a
- Codewerk0.004 USDC
api changelog
POSThttps://code.halowerk.com/v1/api-changelogCompares operations, parameters, request bodies, response codes and media types, component schemas (one property level), servers and security schemes of two documents (Swagger 2.0 is converted with swagger2openapi first; 3.0 and 3.1 are rea