{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "Vibgrate Newsroom",
  "description": "Official Vibgrate announcements: dated, factual press releases with verifiable sources.",
  "home_page_url": "https://vibgrate.com/newsroom/",
  "feed_url": "https://vibgrate.com/newsroom/feed.json",
  "icon": "https://vibgrate.com/img/logo.png",
  "language": "en-US",
  "items": [
    {
      "id": "https://vibgrate.com/newsroom/2026/08/19/token-savings-benchmark-300-file-repository/",
      "url": "https://vibgrate.com/newsroom/2026/08/19/token-savings-benchmark-300-file-repository/",
      "title": "Vibgrate benchmark measures 26.3% fewer tokens on a 300-file repository",
      "summary": "In Vibgrate's latest pinned A/B benchmark, an AI coding assistant using Vibgrate AI Context consumed 493,895 tokens, against 670,169 with generic file discovery — 26.3% fewer across the approximately 300-file test tier.",
      "content_text": "In Vibgrate's latest pinned A/B benchmark, an AI coding assistant using Vibgrate AI Context consumed 493,895 tokens, compared with 670,169 tokens using generic file discovery — 26.3% fewer across the approximately 300-file test tier. Both runs used the same model and tasks, and only tasks successfully completed by both configurations were included.\n\nThe published results also show that the code map increased token use on very small repositories and produced larger savings on the approximately 1,000-file test case. Repository size changes the economics: mapping a five-file project costs more than it saves, while on larger codebases the map reduces repeated repository searching.\n\nThe complete figures are measured in detail on the token savings benchmark page, which publishes the methodology, task-level results, model, CLI version, and verifier approach for every pinned run.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/07/23/ai-context-listed-in-mcp-registry/",
      "url": "https://vibgrate.com/newsroom/2026/07/23/ai-context-listed-in-mcp-registry/",
      "title": "Vibgrate AI Context listed in the official MCP Registry",
      "summary": "The local-first, read-only server gives compatible coding assistants access to version-correct library documentation, a repository code map, and offline drift information through the Model Context Protocol.",
      "content_text": "Vibgrate AI Context is now listed in the official Model Context Protocol (MCP) Registry as com.vibgrate/ai-context.\n\nThe local-first, read-only server gives compatible coding assistants access to version-correct library documentation, a repository code map, and offline drift information through MCP. It runs on the developer's machine over the working tree, requires no account, and reduces repeated repository searching by letting the assistant discover relevant code through the map.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/07/17/vibgrate-for-vs-code-on-marketplace/",
      "url": "https://vibgrate.com/newsroom/2026/07/17/vibgrate-for-vs-code-on-marketplace/",
      "title": "Vibgrate for VS Code published to the Visual Studio Marketplace",
      "summary": "The extension brings a locally computed DriftScore and per-dependency version drift into the editor, using the same scoring engine as the Vibgrate CLI.",
      "content_text": "Vibgrate for VS Code is now available through the Visual Studio Marketplace.\n\nThe extension brings a locally computed DriftScore and per-dependency version drift into the editor, using the same scoring engine as the Vibgrate CLI. Scores are computed on the developer's machine from the project's own manifests, so the editor shows the same numbers a CI scan reports.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/07/10/risk-and-drift-scoring-methodology-published/",
      "url": "https://vibgrate.com/newsroom/2026/07/10/risk-and-drift-scoring-methodology-published/",
      "title": "Vibgrate publishes open methodology for measuring software drift and risk",
      "summary": "Vibgrate has published the data sources, scoring factors, formulas, and limitations behind DriftScore, RiskScore, and DriftRisk™. The methodology is available under CC BY 4.0 and permanently archived on Zenodo.",
      "content_text": "Software teams are often asked to act on scores they cannot inspect. When a score can block a release, prioritize an upgrade, or support an audit response, an unexplained number becomes a liability.\n\nVibgrate has published the methodology behind DriftScore, its measure of maintainability drift; RiskScore, its measure of current security exposure; and DriftRisk™, the combined view.\n\nThe open-access paper documents the scoring factors, data sources, formulas, evidence hierarchy, and 25 primary references behind the measures. It also identifies the calibration weights derived from Vibgrate scan data that remain proprietary. Teams can inspect and challenge the published method rather than take the scores on trust.\n\nThe software risk and drift scoring methodology whitepaper was first published on July 10, 2026, and archived on Zenodo on July 13, 2026. It is free to read without signing up, available in HTML and PDF, and licensed under CC BY 4.0. The concept DOI identifies the evolving work, while each archived release has its own version-specific DOI for precise citation.\n\nThe source document is also maintained in the open-source Vibgrate CLI repository, where its revision history can be inspected and compared.\n\nTeams can test the published method by running the Vibgrate CLI against their own repositories and comparing the reported factors and scores with the definitions and formulas in the paper.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/06/24/cli-adds-sbom-and-openvex-exports/",
      "url": "https://vibgrate.com/newsroom/2026/06/24/cli-adds-sbom-and-openvex-exports/",
      "title": "Vibgrate CLI adds SBOM and OpenVEX exports",
      "summary": "The CLI can export software bills of materials in CycloneDX and SPDX formats, compare dependency changes between scan artifacts, and generate OpenVEX documents from the same local scanning workflow.",
      "content_text": "The Vibgrate CLI can now export software bills of materials in CycloneDX and SPDX formats, compare dependency changes between scan artifacts, and generate OpenVEX documents from the same local scanning workflow.\n\nAll three outputs come from the scan the CLI already runs, so producing supply-chain evidence adds no separate tooling or account. The original announcement, SBOM and OpenVEX evidence from one command, has the full detail.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/02/19/max-privacy-mode-for-regulated-environments/",
      "url": "https://vibgrate.com/newsroom/2026/02/19/max-privacy-mode-for-regulated-environments/",
      "title": "Vibgrate CLI adds Max Privacy Mode for regulated environments",
      "summary": "A hardened scanning profile suppresses local file writes and disables high-context scanners, for teams in financial services, healthcare, government, and other environments under strict data governance.",
      "content_text": "For teams operating under strict data governance — financial services, healthcare, government — even writing local scan artifacts can require justification.\n\nThe Vibgrate CLI's --max-privacy flag enables a hardened scanning profile that suppresses local file writes and disables high-context scanners entirely, so drift results come from the least data the scan can touch. The original announcement, Max Privacy Mode: hardened drift scanning for regulated and sensitive environments, has the full detail.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/02/16/offline-and-air-gapped-scanning/",
      "url": "https://vibgrate.com/newsroom/2026/02/16/offline-and-air-gapped-scanning/",
      "title": "Vibgrate CLI scans fully offline for air-gapped environments",
      "summary": "Offline mode provides full drift scanning without any network calls, using a downloadable package-version manifest for version lookups — announced alongside the CLI's public npm release.",
      "content_text": "Some environments cannot reach the internet — defense, healthcare, financial services, or simply a laptop on a plane.\n\nThe Vibgrate CLI's offline mode, announced alongside the CLI's public npm release, provides full drift scanning without any network calls, using a downloadable package-version manifest for version lookups. Restricted and air-gapped environments get the same drift intelligence as connected ones. The original announcement, Offline mode and air-gapped scanning, has the full detail.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    },
    {
      "id": "https://vibgrate.com/newsroom/2026/02/16/vibgrate-cli-available-on-npm/",
      "url": "https://vibgrate.com/newsroom/2026/02/16/vibgrate-cli-available-on-npm/",
      "title": "Vibgrate CLI becomes publicly available on npm",
      "summary": "The first public @vibgrate/cli package measures upgrade drift across Node.js and .NET projects and can run locally from the terminal or in CI.",
      "content_text": "Vibgrate has made the Vibgrate CLI publicly available on npm as @vibgrate/cli.\n\nThe first public package measures upgrade drift across Node.js and .NET projects and can run locally from the terminal or in CI. Scans run on the developer's machine against the project's own manifests, with no account required.",
      "date_published": "2026-08-22T00:00:00Z",
      "authors": [
        {
          "name": "Vibgrate",
          "url": "https://vibgrate.com/"
        }
      ],
      "tags": [
        "press release"
      ]
    }
  ]
}