Homebrew Core Formula Bottle & Lifecycle Evidence API
Pricing
from $1.00 / 1,000 metadata observations
Homebrew Core Formula Bottle & Lifecycle Evidence API
Compare exact core formula records for stable version, bottle SHA256 declarations and deprecation/disable state. No Ruby execution, artifacts, casks, aliases or dependency solving.
Pricing
from $1.00 / 1,000 metadata observations
Rating
0.0
(0)
Developer
Salih Can Kurnaz
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Observe current canonical Homebrew/core formula names via the official per-formula JSON API. Require name/full_name and tap to match; do not silently resolve aliases, third-party taps or casks. Keep stable version, formula revision/version scheme, source-archive checksum declaration, declared license expression, bottle rebuild and a sorted platform-to-SHA256 map, plus nullable deprecation/disable flags, dates and reason codes. Bottle keys are provider platform labels and do not prove compatibility with a user machine. No artifact download, checksum recomputation, install, brew/Ruby execution, HEAD selection, dependency resolver, CVE assessment, analytics or safe/approved verdict. Missing source hashes/flags remain unknown. Formula metadata is supplied by Homebrew; per-formula responses may contain analytics and upstream URLs but those are discarded and never followed. Useful for frozen deployment inventories and noticing changed source declarations, not independently validating archive bytes.
Input example
{"formulae": ["wget","jq"],"maxResults": 2}
Outputs and change comparison
One saved observation is one dataset row with itemKey, sourceUrl, contentHash and observedAt. The SHA256 covers only selected semantic fields; retrieval times, API request URLs, download/popularity counters and people are excluded. Copy SNAPSHOT.previousHashes into the next input to compare the same exact watchlist. Statuses are NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. Unchanged observations are still billable. There is no hidden persistent baseline and no missing-row/deletion inference. OUTPUT records actual requestCount, rowsEmitted, source summaries, errors, status and complete. SNAPSHOT.complete is false after any error or when any requested observation could not be delivered. Reaching the selected result cap is PARTIAL_RESULT_CAP; a monetary budget stop is PARTIAL_BUDGET. Provider restrictions produce PARTIAL_PROVIDER_LIMIT. A saved observation means successful metadata extraction only, not an independent validation or entitlement decision.
Pricing and bounded work
$0.005 startup plus $0.001 per saved observation, pay per event. Startup quantity follows Apify memory rules with minimum one. Minimum permitted run budget: $0.0055. Default 256 MB, timeout 120 seconds, no restart. Five identifiers and at most five rows; a 55-second fetch deadline and two-MiB decoded-body cap apply. API requests are made only after checking the affordable result capacity. Zero affordable observations causes zero source requests, including no provider request. Before each later request and dataset write the budget is checked again. Responses that do not produce a saved row are not charged as observations; startup can still apply. No browser, paid proxy, paid external API or credentials. No network retries, bypasses, open-ended search or bulk pagination. Shared-IP provider limits still apply across runs: avoid parallel requests that exceed provider policy and use supported bulk data channels for large extraction.
Failure and access behavior
Only constructed official HTTPS API endpoints are contacted. Only fixed provider endpoints constructed from validated identifiers are contacted. Private addresses and credential-bearing/cross-provider redirects are rejected. HTTP403/429 or Retry-After stops further provider work; successful current responses can be retained. Unknown/missing identifiers are errors, never guessed missing/safe states. All-source failure exits nonzero after preserving OUTPUT; partial delivery preserves successful rows and explicit errors. Source versions and raw declarations can change, and the Actor does not independently verify artifact bytes, publisher identity, signatures or legal rights. Public upstream APIs/data may be free; the fee covers the bounded selection, validation, comparison/output workflow and Apify execution. There is no affiliation, exclusive data access, guaranteed availability, completeness or revenue claim.