Repository binding unavailable
Home automation escalation
You saw a light bulb and answered with a Rust integration that apparently wants to become the household’s entire nervous system.
Historical result · no repository binding was retained
Roasts
evremap
Keyboard diplomacy
evremap suggests that ordinary keyboard layouts were merely a starting point for negotiating a more sophisticated treaty between fingers and operating systems.
atomicparsley
Media archaeology
atomicparsley sounds less like a media utility and more like the tool you bring when a file’s metadata refuses to confess.
docker-stack-deploy
Infrastructure in a bottle
docker-stack-deploy takes the classic ‘this deployment should be simple’ premise and gives it a dedicated Rust project, which is either excellent engineering or a very committed way to avoid clicking buttons.
Category breakdown
Impact
25% weight
Several owned projects appear practically useful and distinctive, spanning home automation, input remapping, media tooling, deployment, and systems utilities. Repository popularity is not used as the basis for this score.
Consistency
15% weight
The visible portfolio shows repeated activity through 2026, with multiple owned repositories updated across several years. The supplied subset supports sustained activity, though it does not provide complete contribution history or explain.
Quality
25% weight
Metadata indicates multiple substantial, maintained owned projects and several mature-looking domains, but the available public metadata does not establish engineering quality.
Depth
20% weight
The portfolio includes long-lived owned projects with updates from 2022 through 2026, plus multiple projects that appear to address nontrivial practical problems. Exact scope and implementation depth are not available.
Breadth
10% weight
The visible repositories span Rust, C++, Python, Java, home automation, desktop/input tooling, media utilities, deployment, parsing, and systems-oriented projects. Forks are treated as limited evidence of owned breadth.
Community
5% weight
The profile has substantial followers and several repositories have visible stars, providing a weak positive signal of community attention. This category does not affect the other scores.
Stats
52-week commit heatmap
258 active daysLanguage distribution
5 langs
- Rust50%
- Python17%
- Unknown17%
- C++8%
- Java8%
Based on the bounded repository sample saved with this analysis.
Numbers
Owned repos
Non-fork sample
9
Commits
Last 12 months
1699
Followers
Accepted fact
3863
Joined GitHub
Profile date
Aug 2009
Top repos
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
wez /
govee2mqtt
84/100
A substantially starred, actively maintained Rust home-automation integration, indicating practical utility and sustained ownership.
OwnedActiveProfile ratingRust
★ 1413 · 2mo agoOpen on GitHub ↗
wez /
evremap
80/100
A maintained Rust input-remapping project with substantial visible interest and a focused systems-tooling premise.
OwnedActiveProfile ratingRust
★ 643 · 2y agoOpen on GitHub ↗
wez /
atomicparsley
78/100
A long-lived C++ media-related project with substantial visible interest and a recent update, suggesting durable usefulness.
OwnedActiveProfile ratingC++
★ 753 · 2y agoOpen on GitHub ↗
wez /
govee-lan-hass
72/100
A maintained Python home-automation project with meaningful visible interest and a clear practical domain.
OwnedActiveProfile ratingPython
★ 224 · 2y agoOpen on GitHub ↗
wez /
wiff
70/100
An actively updated Rust project with a distinctive name and evidence of ongoing ownership; the supplied metadata does not reveal its purpose or implementation scope.
OwnedActiveProfile ratingRust
★ 97 · 2d agoOpen on GitHub ↗
wez /
docker-stack-deploy
57/100
An actively updated Rust deployment project with a practical infrastructure-oriented premise, though the metadata alone does not establish its maturity.
OwnedActiveProfile ratingRust
★ 22 · 8mo agoOpen on GitHub ↗
wez /
eledo
53/100
A Rust project with multi-year continuity and moderate visible interest, providing credible evidence of sustained ownership.
OwnedActiveProfile ratingRust
★ 47 · 4y agoOpen on GitHub ↗
wez /
govee-py
48/100
A Python project maintained into 2023 with a practical-looking ecosystem relationship, but limited evidence of recent continuation.
OwnedActiveProfile ratingPython
★ 42 · 3y agoOpen on GitHub ↗
wez /
jlexphp
46/100
A Java project with multi-year age and modest visible interest, indicating real but comparatively older portfolio activity.
OwnedActiveProfile ratingJava
★ 34 · 5y agoOpen on GitHub ↗
wez /
lockbud
35/100
A non-archived Rust fork updated in 2025; it provides limited evidence of original ownership because the metadata identifies it as a fork.
ForkActiveProfile ratingUnknown
★ 4 · 1y agoOpen on GitHub ↗
wez /
rmk
30/100
A recently updated fork with minimal visible interest; the available metadata supports little inference beyond continued activity.
ForkActiveProfile ratingUnknown
★ 1 · 2y agoOpen on GitHub ↗
wez /
ssh2-rs
25/100
An older Rust fork with no visible stars; it is evidence of repository activity but weak evidence of distinctive owned work.
ForkActiveProfile ratingRust
★ 0 · 5y agoOpen on GitHub ↗
Timeline
- Joined GitHub
- Created wez/jlexphp - A lexer generator for PHP. It is based on JLex and requires Java to generate the lexer. Once generated, the lexer only requires PHP to run.
- Created wez/atomicparsley - AtomicParsley is a lightweight command line program for reading, parsing and setting metadata into MPEG-4 files, in particular, iTunes-style metadata.
- Created wez/ssh2-rs - Rust bindings for libssh2
- Created wez/evremap - A keyboard input remapper for Linux/Wayland systems, written by @wez
- Created wez/eledo - Increase or reduce the privilege level of the calling code on Windows systems
- Created wez/govee-lan-hass - Control Govee lights via the LAN API from Home Assistant
- Created wez/govee-py - Control Govee Lights from Python
- Created wez/govee2mqtt - Govee2MQTT: Connect Govee lights and devices to Home Assistant
- Created wez/docker-stack-deploy - GitOps automation for plain old docker compose stack deploy
- Created wez/rmk - Rust keyboard firmware library with layers, macros, real-time keymap editing, wireless(BLE) and split support
- Created wez/lockbud - Statically detect memory, concurrency bugs and possible panic locations for Rust.
- Created wez/wiff - sniff out the wiff in your diff, from the comfort of your terminal. wiff is a terminal-centric code review tool
- Most recent push to wez/wiff
Compare
WEZ · 6DMEDIAN CODER
Rubric
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 82 | 20.50 |
| Quality | 25% | 69 | 17.25 |
| Depth | 20% | 76 | 15.20 |
| Consistency | 15% | 78 | 11.70 |
| Breadth | 10% | 74 | 7.40 |
| Community | 5% | 63 | 3.15 |
Impact · 82/100
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for wez. Several owned projects appear practically useful and distinctive, spanning home automation, input remapping, media tooling, deployment, and systems utilities. Repository popularity is not used as the basis for this score.
Quality · 69/100
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for wez. Metadata indicates multiple substantial, maintained owned projects and several mature-looking domains, but the available public metadata does not establish engineering quality.
Depth · 76/100
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for wez. The portfolio includes long-lived owned projects with updates from 2022 through 2026, plus multiple projects that appear to address nontrivial practical problems. Exact scope and implementation depth are not available.
Consistency · 78/100
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for wez. The visible portfolio shows repeated activity through 2026, with multiple owned repositories updated across several years. The supplied subset supports sustained activity, though it does not provide complete contribution history or explain.
Breadth · 74/100
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for wez. The visible repositories span Rust, C++, Python, Java, home automation, desktop/input tooling, media utilities, deployment, parsing, and systems-oriented projects. Forks are treated as limited evidence of owned breadth.
Community · 63/100
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for wez. The profile has substantial followers and several repositories have visible stars, providing a weak positive signal of community attention. This category does not affect the other scores.
- Raw total
- 75.20
- Top-end curve
- +0.00
- Final overall
- 75.2
Tier thresholds
S 90-100 Mass-producing humansA 80-89 Ship machineB 70-79 Solid engineerC 60-69 Getting thereD 40-59 README enthusiastF 0-39 GitHub tourist
I. How this saved profile rating was produced
- 01
Validate. The server validates the login, signed browser session, attempts, cooldown, daily ceiling, and the single provider permit.
- 02
Collect. The VPS collector reads bounded public profile metadata and up to 12 recent repository metadata rows in volatile memory.
- 03
Rate. One pinned provider returned a closed profile-rating object with no tools, browsing, shell, or repository-content access.
- 04
Verify. Server checks bound the subject, rejected unsafe or echoed text, validated the schema, and recomputed rubric-v3 final arithmetic.
- 05
Save. Only a valid completion and allowlisted post-completion facts commit atomically; the public projection is then rebuilt.
This saved profile analysis is metadata-only and did not read repository trees, README files, or source code. Availability of new analysis is separate from this historical result.
Rated 2026-08-10 · rating-rubric/3
II. Data sources & caveats
- Scores summarize one accepted, subject-bound analysis; they are not a security audit or endorsement.
- Rank, percentile, and median use 1095 currently accepted public profiles and can change as the leaderboard changes.
- Repository and language details reflect the bounded analyzed sample, not necessarily every repository.
- Missing data is shown as unavailable or not evaluated instead of being inferred as zero.
- Analysis completed Aug 10, 2026, 2:17 AM UTC and is marked aging.