NewYou can now follow repositories and track contribution activity in one place.
Flux
GitHub

Open-source identity / public contributor signal

Your OSS work deserves visibility.

Open-source work is fragmented and difficult to showcase. Flux helps contributors organize their work, stay on top of relevant opportunities, and build a credible public identity around their contributions.

Start with GitHubWatch demo
Track ContributionsBuild OSS CredibilityRepository WorkspacesContribution InsightsRelevant Issue AlertsPublic OSS ProfilesOpen Source PortfolioContribution StreaksRepository WatchlistsContributor IdentityShowcase Real ImpactStay ConsistentTrack ContributionsBuild OSS CredibilityRepository WorkspacesContribution InsightsRelevant Issue AlertsPublic OSS ProfilesOpen Source PortfolioContribution StreaksRepository WatchlistsContributor IdentityShowcase Real ImpactStay Consistent

Workspace

PRs, issues, notes

Smart matches

Focus areas and past PRs

OSS portfolio

Real contribution history

Live alerts

Repo sync and notifications

OSS identity problem / fragmented public signal

Your OSS work has depth. Your public signal should too.

Flux starts from the gap between meaningful contribution and how difficult it still is to read a contributor quickly and confidently without tab sprawl.

01

GitHub shows activity, but not a readable identity.

Important work disappears into pull request threads, release notes, and review discussions that never become legible at a glance.

02

Credibility gets fragmented across repos and context.

Repository depth, review quality, issue selection, and consistency all matter, but they live in disconnected surfaces with no coherent public shape.

03

Workflow turns into attention debt.

Saved issues, active pull requests, follow-ups, and watched repositories pile up fast, especially when you contribute across multiple projects.

Flux is designed for the moment a contributor wants their work to feel coherent, credible, and visibly alive, without manual curation.

Opportunity radar / watched repositories

Find issues matched toyour skills and pastwork

Flux connects a contributor profile to fresh open-source issues with a visible reason trail, so the next contribution feels obvious instead of accidental.

01

User intent first

A contributor sets the repositories they want to watch, then Flux keeps the feed constrained to that intent.

02

Explain the match

Each issue carries the repo, score, freshness, and exact reasons it fits the person on the left.

03

Move without noise

The goal is not another dashboard. It is a quiet handoff from profile signal to a useful next contribution.

Public portfolio / generated OSS identity

Your OSS identity, ready to share.

Generated OSS identity, featured contributions, and a public share route in one recruiter-readable portfolio.

Build yours with GitHubSee final call

Generated identity

A concise role and summary shaped from contribution evidence.

Featured work

Pull requests become recruiter-readable proof of depth.

Live portfolio preview

/@david-parker

Scroll inside the frame

D

David Parker

@david-parker Frontend Systems Engineer

Identity summary

Builds open-source dashboard systems with a strong pattern of state modeling, contribution workflows, and repository intelligence.

Expertise

Open-source contributorDeveloper experience builderRepository workflow specialist
0

Merged PRs

0

Repositories

SELECTED WORK

Proof of depth.

A curated collection of the open-source work that best reflects this contributors impact.

flux-labs/runtime-core·Jun 10, 2026

Normalize repository contribution profiles before rendering summaries

Refined the profile normalization path so repository activity, portfolio highlights, and opportunity matching share the same contributor signal.

Connected product-facing identity output to the underlying contribution model, reducing inconsistency across multiple dashboard surfaces.

TypeScriptNext.jsReact Query
HighState modelingSignal normalization
Complexity86
Impact92
Collaboration78
flux-labs/workspace·Jun 7, 2026

Stabilize active PR workspace grouping across review states

Improved grouping for review-needed, blocked, stale, and CI-failed pull requests so contributors can understand active work faster.

Demonstrates strong attention to operational product quality and contributor workflow clarity.

TypeScriptReactZustand
MediumEdge Case handlingOperational UX
Complexity74
Impact81
Collaboration83

Technical footprint

The stack, broken down.

A compact map of the languages, problem domains, and ecosystems visible across this engineer's open-source work.

Languages

TypeScriptRustGo

Domains

Frontend SystemsObservabilityAPI Design

Ecosystems

Next.jsReact QueryPostgreSQL

Current activity

Work in motion.

Recent repository focus and open pull requests, shaped from the same contribution data that powers the rest of the portfolio.

Active repositories

flux-labs/runtime-core

TypeScript ·Last activity Jun 14, 2026

0

Open PRs

0

Merged

flux-labs/design-system

TypeScript ·Last activity Jun 11, 2026

0

Open PRs

0

Merged

Open PRs

Add portfolio preview controls for generated identity sections

flux-labs/runtime-core

PortfolioIdentityFrontend

Insights

Contribution notes.

Short readouts that feel closer to an editor's note than a metrics tile.

CONSISTENCY

14 active days show current contribution momentum, not just historical activity.

FOCUS

flux-labs/runtime-core is the clearest current repository focus, with 148 merged pull requests tracked.

DEPTH

32 repositories show repeat activity, a stronger signal than one-off contribution scatter.

GROWTH

Dashboard architecture is the strongest technical signal across 438 tracked GitHub contributions.

Recruiter summary

Hiring readout.

Evidence is strongest for frontend TypeScript work across dashboard architecture and contribution workflows. The profile looks focused and credible, with most proof concentrated in runtime-core and design-system work.

Built with Flux

Your OSS deserves visibility

Create your ownHomepage

From contributors / real signal

The impact Flux is having on open-source journeys.

Flux makes my OSS work legible: not just what I shipped, but what kind of work I do and how consistently I show up.

Anonymous contributor

My workflow stopped feeling like tab debt. Active PRs, saved issues, and repo focus live in one place now.

Anonymous contributor

The portfolio preview is the difference: I can ship work and keep my public signal coherent without manual curation.

Anonymous contributor

Build your OSS identity.
Start in two minutes.

Connect GitHub. Get matched to issues in repositories you already know. Build a portfolio that proves it.

Repository Workspace

Watch repositories, see contribution recency, and understand PRs, saved issues, reviews, and opportunity counts at a glance.

Relevant Opportunities

See issues matched to repositories you already watch and save the ones worth returning to.

vercel/next.js / #74218

UI

Route transition flashes stale layout...

facebook/react / #31842

HOOKS

Suspense boundary replays stale state...

microsoft/vscode / #229104

API

Extension host stalls while indexing...

Work Memory

Keep saved issues, blocked work, reviews, and repository notes connected to the repo you are ready to contribute to.

Start for FreeView Public Demo