globahire
A personal job radar: watch public job boards for roles that match your stack, and get told the moment one drops. Local, zero dependencies, alerts only.
Install
pipx install git+https://github.com/mgkvibez/globahire.git
Three things you can do
# 1. start a profile, then edit the stack and roles
globahire init
# 2. one pass over the boards; exits 3 when there is something new (cron-friendly)
globahire check --profile profile.yaml
# 3. keep watching every 30 minutes and alert through Telegram as well
export GLOBAHIRE_TELEGRAM_BOT_TOKEN=... GLOBAHIRE_TELEGRAM_CHAT_ID=...
globahire watch --profile profile.yaml --interval 30 --notify terminal,telegram
globahire sources lists the boards. Greenhouse and Lever need a company token: --board greenhouse=acme.
Why this exists
Job alerts are either too noisy, too late, or behind an account that wants to sell your data. The parts that actually matter are small: a profile you control, a filter that is honest about what it dropped, and a dedupe store so a reposted role does not ping you twice.
Two honest limits, by design:
- It does not apply for you. Auto-applying gets accounts banned, and a wrong application sent at machine speed is worse than a missed one. Drafting assistance is V0.2; application queues only for boards with real APIs are V0.3.
- No logged-in scraping. LinkedIn and Indeed are not supported, because scraping them breaks their terms and your account. Supported boards are public JSON endpoints.
How it works
profile.yaml is parsed by a deliberately small reader that understands top-level keys, scalars, inline lists and block lists, and refuses what it does not understand rather than silently dropping a filter, because a dropped filter means missed jobs.
Matching runs filters first (remote-only, exclusions, locations), then scores: a stack hit is 2 points, a role hit is 3, and a job needs min_match (default 1) to count. Every match carries its reasons, so a false positive is easy to explain.
Dedupe is a stable hash of company + title + location, stored in .globahire/seen.json and written atomically. Same role on two boards announces once; a repost tomorrow announces zero times.
Exit codes are a contract: 0 nothing new, 3 new matches, 2 something you must fix (bad profile, unknown board, missing credential).
Contributing
Issues and PRs are welcome. Run bash scripts/verify.sh before pushing; it is the same gate CI runs. New boards are a parser function plus a fixture: no network in tests, ever.
License
MIT
Metadata
Release files for globahire 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| globahire-0.1.0.tar.gz | 17.0 kB | With provenance | Details for globahire-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| globahire-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for globahire-0.1.0-py3-none-any.whl |
Total release size: 32.0 kB
Release files / globahire-0.1.0.tar.gz
| Download URL | globahire-0.1.0.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c6a339033f355b68378b467998daa0bfd170df603b176bd70ddeb73e3f633b5
|
|
BLAKE2b-256 checksum How to use checksums |
c03c27373296d1c9f79d6f157cb359eeee8867cefc182f8519af40f2285ed39c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / globahire-0.1.0-py3-none-any.whl
| Download URL | globahire-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f05755893dd77ab54f1a3ac60c5574984dd220fc2ffa4a7e2dc2b3974f16e887
|
|
BLAKE2b-256 checksum How to use checksums |
5fb200cfa636a09d295c28d9e0313f8aae5cb1ac2d1c900cf1e4e87b2b7e7410
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for globahire 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for globahire-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.