GitHub activity on your portfolio.

GitHub exposes two main APIs for reading public activity. The REST API v3 events endpoint at /users/USERNAME/events returns a paginated stream of recent public events (PushEvent, PullRequestEvent, CreateEvent for releases and tags, IssueCommentEvent, WatchEvent for stars, ForkEvent). It is freely accessible without authentication and rate-limited to 60 requests per hour per IP, which is enough for most widgets that cache responses. The GraphQL API v4 is required for the signature contribution graph data: it exposes contributionsCollection.contributionCalendar with daily counts and color levels, plus pinnedItems for the repositories you pinned on your profile. GraphQL requires authentication and gives you a 5000/hr rate limit. A serious GitHub widget uses both: REST for events, GraphQL for the contribution graph and pinned repos. Poper does exactly this, caches responses on a global edge so your visitors never hit GitHub directly, and refreshes from origin every 6 hours on Free or 30 minutes on Pro.

The green-square calendar that appears on every GitHub profile is one of the most recognizable visualizations on the modern web. It is also one of the strongest proof-of-work signals available to developers: 52 weeks by 7 days of square dots, each colored by how many contributions you made that day. Recruiters scan it in seconds. Open-source users use it to judge whether a maintainer is still active. Build-in-public devs use it to prove momentum to a Twitter or X audience. The data comes from the GraphQL contributionsCollection.contributionCalendar field, returns up to a year of daily counts, and is fully recolorable. Embedding the graph on your own portfolio (rather than linking out to github.com) keeps visitors on your domain, lets you theme the colors to match your brand, and means the visual itself becomes indexable content under your URL.

Since 2020 the build-in-public movement has fundamentally changed how developers market themselves. Indie hackers ship in the open, livestream their commits, and use GitHub Sponsors to fund their work directly from the audience that watches them code. GitHub Sponsors paid out over $40 million to maintainers since launch, and the program now supports 100+ countries. A live activity widget on your personal site is the highest-leverage marketing asset for this audience: it pairs perfectly with a Sponsor button, a newsletter signup, and a Bento or Linktree-style hub. The signal is honest (it is your real commits, not a curated highlight reel), updates without your effort, and feels authentic in a way that AI-generated landing copy cannot. For maintainers raising sponsorship, an embedded contribution heatmap plus the latest release timeline is the closest thing to a financial statement that open source has.

GitHub profile READMEs (introduced in 2020 as the README in a special repo named after your username) made every developer their own publisher. Today profile READMEs contain stats cards, language graphs, contribution streaks, GitHub Sponsors badges, and even auto-generated blog post summaries. The limitation: profile READMEs only render on github.com and only support static images via shields.io or vercel-hosted SVG endpoints. A widget on your own personal site (.dev domain, GitHub Pages, or any static host) breaks past those limits. You get interactive cards, real-time data, custom layouts, theming beyond color, and SEO benefit (because the embedded content is indexable HTML on your domain). The dev portfolio market has matured: tools like brittanychiang.com, leerob.io, and fly.io's engineering page set the bar, and they all share the same pattern of live GitHub data integrated directly into the portfolio rather than as an external link.

Senior engineers and engineering managers will Lighthouse your portfolio. They will. It is half curiosity and half a screening signal. A portfolio with a 95+ Lighthouse score reads as someone who actually cares about the craft, while a 60-score portfolio with a janky GitHub embed reads as someone who copy-pasted their resume. Widgets are notorious Lighthouse killers: synchronous JavaScript blocking the main thread, layout shift from images that load late, blocking network requests to GitHub on every visit. The Poper GitHub Activity Widget is engineered for this audience: async loading below the fold, scoped CSS that cannot leak into your design system, edge-cached responses so visitors never hit GitHub directly, dimensions reserved on every element to keep CLS at zero, and the entire bundle gzipped under 40KB. Embed it on a Next.js, Astro, or Hugo portfolio and your Lighthouse score will not move. That matters more for a developer site than for any other vertical, because your audience is the one running the audit.