VersionTruth

Validates npm, Node, and GitHub Actions version pins against live registry data to prevent hallucinations. Checks for outdated, deprecated, or EOL versions and suggests upgrades.

Sby Skills Guide Bot
DevelopmentIntermediate
107/24/2026
Claude CodeCursorWindsurfCopilotCodex
#versions#ci#dependencies#hallucination-mitigation#npm#node#github-actions#agents#nanda

Recommended for


name: "VersionTruth" description: "The antidote to version hallucinations: real-time ground-truth for npm, Node, and GitHub Actions." version: "1.1.0" emoji: "🛡️" author: "Ariel Anders" github: "arii" tags: ["versions", "ci", "dependencies", "hallucination-mitigation", "npm", "node", "github-actions", "agents", "nanda"] metadata: openclaw: requires: bins: - "curl" - "jq"

Instructions

  1. Before pinning, editing, or correcting any dependency or runtime version pin in package.json, .nvmrc, .node-version, or a .github/workflows/*.yml uses: line, identify the candidate version string you intend to write.
  2. Query GET https://boomtick.blog/api/compare-version?ecosystem={ecosystem}&name={name}&candidate={candidate} or use the POST https://boomtick.blog/api/batch-compare endpoint to validate multiple candidates at once.
  3. Inspect the comparison results: verify isOutdated, isCurrent, isDeprecated (npm-only), and isEOL (node-only) statuses.
  4. If a version is outdated, deprecated, or EOL, evaluate upgrading to the returned latest version instead.

Rules

  • Never downgrade an existing version string in the repo simply because it is unfamiliar or not recognized from your training data cutoff.
  • Treat unfamiliar version strings as a signal to check VersionTruth, not as evidence of a typo or error.
  • Keep version changes minimal and additive, validating each proposal against live registry data.
  • Responses are cached for 30 minutes at the edge; do not hammer the endpoints with repeated requests for the same package/version within a single session.
  • The name parameter maps as follows: the npm package name for npm (e.g. pnpm), the GitHub repository path for gh-action (e.g. actions/checkout), and is omitted or set to node for the node ecosystem.

Error Handling

  • If the API request fails or the endpoint is unreachable, do not guess or revert; leave the version pin unchanged and note in your execution logs that the check could not be completed.
  • If a package name format or query parameter is invalid, report the validation error to the user immediately. Validation errors return 400 with { "error": "<message>" }.
  • Requests are rate-limited to 100 per 15-minute window per IP. A rate-limited response returns 429 with X-RateLimit-Remaining: 0; back off until the timestamp in X-RateLimit-Reset rather than treating this as a hard failure.

API Specification

Base URL: https://boomtick.blog/api

Note: All resource paths listed below must be appended directly to the Base URL (e.g. Base URL + /latest-version resolves to https://boomtick.blog/api/latest-version). Do not duplicate slashes.

GET /skill.md

Returns this SKILL.md file dynamically as raw Markdown, allowing self-discovery of these endpoints at runtime.

Example request:

curl -s "https://boomtick.blog/api/skill.md"

GET /health

Lightweight health check endpoint returning service status.

Example request:

curl -s "https://boomtick.blog/api/health"

Example response:

{
  "status": "ok",
  "service": "VersionTruth",
  "checkedAt": "2026-07-10T08:30:00.000Z"
}

GET /latest-version

Returns the current latest version for a package, runtime, or action.

| param | required | values | |---|---|---| | ecosystem | yes | npm | node | gh-action | | name | required unless ecosystem=node | npm package name, or owner/repo for gh-action |

Example request:

curl -s "https://boomtick.blog/api/latest-version?ecosystem=gh-action&name=actions/checkout"

Example response:

{
  "ecosystem": "gh-action",
  "name": "actions/checkout",
  "latest": "v4.2.2",
  "checkedAt": "2026-07-10T08:30:00.000Z"
}

GET /compare-version

Tells you whether a candidate version is outdated, current, or ahead of the real latest. Includes npm deprecation warnings (isDeprecated) and Node EOL warnings (isEOL).

| param | required | values | |---|---|---| | ecosystem | yes | npm | node | gh-action | | name | required unless ecosystem=node | npm package name, or owner/repo | | candidate | yes | the version string the agent is about to use |

Example request:

curl -s "https://boomtick.blog/api/compare-version?ecosystem=gh-action&name=actions/checkout&candidate=v4" | jq '.isOutdated'

Example response:

{
  "ecosystem": "gh-action",
  "name": "actions/checkout",
  "candidate": "v4",
  "latest": "v4.2.2",
  "isOutdated": true,
  "isCurrent": false,
  "isAheadOfLatest": false,
  "isDeprecated": null,
  "isEOL": null,
  "checkedAt": "2026-07-10T08:30:00.000Z"
}

POST /batch-compare

Allows querying comparison results for up to 25 items concurrently. Requests exceeding this limit are rejected with 400.

Example request:

curl -s -X POST -H "Content-Type: application/json" \
  -d '[
    { "ecosystem": "npm", "name": "pnpm", "candidate": "9.0.0" },
    { "ecosystem": "gh-action", "name": "actions/checkout", "candidate": "v4" }
  ]' \
  "https://boomtick.blog/api/batch-compare"

Example response:

[
  {
    "ecosystem": "npm",
    "name": "pnpm",
    "candidate": "9.0.0",
    "latest": "10.28.2",
    "isOutdated": true,
    "isCurrent": false,
    "isAheadOfLatest": false,
    "isDeprecated": false,
    "isEOL": null
  },
  {
    "ecosystem": "gh-action",
    "name": "actions/checkout",
    "candidate": "v4",
    "latest": "v4.2.2",
    "isOutdated": true,
    "isCurrent": false,
    "isAheadOfLatest": false,
    "isDeprecated": null,
    "isEOL": null
  }
]

Changelog

1.1.0

  • Introduced /api/batch-compare POST endpoint (max 25 items) for concurrent checks.
  • Refactored deprecation and EOL checks into clean ecosystem-specific isDeprecated and isEOL fields.
  • Added /api/health health verification route.
  • Integrated IP-based rate limiting (100 req / 15 min / IP) on all endpoints.
  • Hardened registry lookups against SSRF (strict owner/repo allowlist on GitHub Actions fetcher) and path traversal (dev server API resolver uses containment check + identifier allowlist).
Related skills