{"uid":"cap_zInTinHY3fdGGeShAbp5d","slug":"paket-release-cadence-analyzer-b66ff1a1","name":"Paket Release Cadence Analyzer","description":"Looks at when a package published, not how often, and reports where the pattern breaks. Three kinds of finding, which mean different things and are kept apart. A long gap: a silence several times the package own median interval, which suggests dormancy. A burst: several releases inside a short window, which is either emergency fixes or an automated publish loop that ran away, and the response gives the dates so the reader can tell.","url":"https://paket.halowerk.com/v1/release-cadence","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"name":{"type":"string","maxLength":300,"minLength":1},"system":{"enum":["npm","pypi","maven","go","cargo","nuget","rubygems"],"type":"string"},"sensitivity":{"enum":["low","normal","high"],"type":"string","default":"normal","description":"How far from the median counts as an anomaly. low = 5x median gap, normal = 3x, high = 2x."},"include_prereleases":{"type":"boolean","default":false}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.004","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.004/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.004","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.004","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_gfgIjxzvKBN8r84hM6eTy","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.004","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Analyzes the release timing history of a package to detect cadence anomalies — specifically long dormancy gaps and burst release clusters — and reports where the pattern breaks.","exampleAgentPrompt":"Can you check the release cadence of the lodash npm package and flag any long dormancy gaps or burst release clusters in its history?","exampleUseCases":[{"title":"Detecting dormant dependency in CI","prompt":"We're using left-pad in production — can you analyze its release cadence and tell me if it's gone dormant or had any suspicious release bursts recently?"},{"title":"Auditing automated publish pipeline","prompt":"Our bot may have triggered a runaway publish loop for our internal package @acme/utils — can you check the release cadence and flag any bursts where multiple releases happened in a short window?"},{"title":"Evaluating open source package health","prompt":"Before we add react-query to our project, can you look at its release timing history and tell me if there are any long gaps or unusual burst patterns that might signal instability?"}],"resultDescription":"A structured report with up to three categories of cadence findings: long dormancy gaps (silences several times the package's own median interval), burst clusters (multiple releases within a short window), and normal cadence confirmation. Burst findings include the specific dates so the caller can distinguish emergency fixes from runaway automation.","failureModes":["Package not found in the specified ecosystem — returns an error or empty findings","Package has too few releases to establish a meaningful median interval","Ecosystem not supported — returns a validation error","Malformed package name input — returns a 400-level error","Network or upstream registry timeout causing a 5xx response"],"whenToPreferThis":"Use this endpoint when you specifically need to analyze release timing anomalies — dormancy gaps or burst clusters — rather than general maintenance health signals (use the maintenance scoring endpoint for that). Prefer this when you want to understand whether a package's release cadence has structurally broken down, whether an automated publish process may have misbehaved, or whether a long silence suggests effective abandonment.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T12:32:12.472Z","isFirstParty":false}