mrkeyoor.comAsk

emmabostian/developer-portfoliostested 03 Oct 2026commit 39bb80c

developer-portfolios review

Developer Portfolios is useful for finding examples before writing or redesigning a personal site.

  • Install 6 s
  • Build 1 s
39/39tests passed
  • 35 packages
Dev Toolsevaluationupdated 30 Oct 2026
+68stars / 7d

Developer Portfolios is an alphabetical directory of developers' personal websites. Some entries include a role or specialty. Use it to find examples of how people present their work, then inspect the linked sites against the needs of your own audience.

Verdict

Developer Portfolios is useful for finding examples before writing or redesigning a personal site. Our run recorded a successful build and 39 passing pytest tests, but the supplied results do not establish the coverage or quality of external portfolios. Start with a role relevant to yours, inspect the destination and compare how clearly it explains the person's work.

We ran it

Lab card: what happened when we ran developer-portfolios
Lab card from our sandbox run
Screenshot of developer-portfolios (github.com/emmabostian/developer-portfolios)
github.com/emmabostian/developer-portfolios
Install✓ · 6s35 packages · 37 MB
Build✓ · 1s
Tests✓ · 2s39 passed · 0 failed of 39 (pytest)
Known vulns0(pip-audit)
Repo25 files~1,986 lines of source · 0.6 MB · 2 CI workflows · tests dir

Answers from our run

Does developer-portfolios build from source?

Dependencies installed in 6 seconds (35 packages), and the build succeeded in 1 seconds. We cloned commit 39bb80c into a clean Debian container with 3 CPUs and no project-specific setup.

Do developer-portfolios's tests pass?

Yes. The project's own test command finished in 2 seconds and reported 39 passed, 0 failed (pytest).

Does developer-portfolios have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use developer-portfolios?

Readers expecting a portfolio website codebase to deploy.

What are the alternatives to developer-portfolios?

Portfolio Ideas, Awesome Portfolio Websites. Developer Portfolios is useful for finding examples before writing or redesigning a personal site.

Setup4/5On the five-point rubric below, browsing has a straightforward documented path and the supplied repository installation and build succeeded. This supports a 4 for access and initial evaluation. It does not establish deployment behavior or compatibility across environments.
Docs3/5The README states the collection's purpose, and the contribution checklist specifies ordering, link checks and generated-file handling. Those support a useful browsing and submission path. The longer guide mixes branch references, so its Git instructions require care.
Community5/5Last push on 2026-10-29 and 27,700 stars.Editor’s note: The contribution guide welcomes feedback and pull requests, but that invitation does not establish maintainer response times or support capacity. The inaccessible activity endpoints are excluded from this assessment.
Maturity2/5No tagged GitHub release, repository created 2019-09-13, its test suite passed in our sandbox (39 of 39 passed) and no licence file GitHub recognises.Editor’s note: The supplied build and test results describe one checkout. Without test implementation extracts or a systematic destination review, they cannot support a numerical assessment of directory-wide reliability or maintenance coverage.

How we score

Who it’s for

Developers researching how to explain projects on a personal website.
Mentors helping students compare portfolio content and navigation.
Contributors looking for a documented Markdown submission task.

Who it’s NOT for

Readers expecting a portfolio website codebase to deploy.
People seeking an editorial ranking of the best designs.
Dataset users who require independently verified availability of every destination.

Setup reality

Our October 3, 2026 sandbox run at commit 39bb80c completed installation in 6 seconds, recording 35 dependencies and 37 MB on disk. The build succeeded in 1 second. Pytest completed in 2 seconds with 39 passed and 0 failed of 39. Pip-audit reported 0 known vulnerabilities. These are repository measurements, not results from testing the linked portfolios.

You can browse the README in a browser without installing the repository. To submit a site, the contribution guide describes forking the repository, adding an entry in first-name order and opening a pull request. Its checklist says to leave the generated feed.json unchanged.

The recorded sandbox configuration was 3 CPUs, 8 GB RAM and image ghcr.io/astral-sh/uv:python3.12-bookworm. The image label does not establish the actual runtime or operating-system version. The supplied results do not identify which external destinations, if any, the tests contacted. They also do not establish that the hosted directory application works. Open each shortlisted portfolio before relying on it.

Find examples, then choose your own criteria

Developer Portfolios can help you find personal websites to study. Its alphabetical order cannot tell you which example fits a backend engineer applying for a job or a consultant explaining specialist work. Begin with the audience your own site needs to serve.

The README describes the collection as inspiration. Entries pair names with links, sometimes followed by a role or specialty. Use those labels to find candidates, then inspect what each destination explains. A role label is a starting point for browsing, not a review of the person's work.

What happened when we ran it

Our October 3, 2026 sandbox run at commit 39bb80c completed installation in 6 seconds, recording 35 dependencies and 37 MB on disk. The build succeeded in 1 second. Pytest completed in 2 seconds with 39 passed and 0 failed of 39. Pip-audit reported 0 known vulnerabilities.

The checkout contained 25 files, approximately 1,986 source lines and 0.6 MB. The scan found a tests directory and 2 CI workflow files, with no Dockerfile. The recorded configuration was 3 CPUs, 8 GB RAM and image ghcr.io/astral-sh/uv:python3.12-bookworm. That image name does not verify the executing Python or operating-system version.

The supplied results report successful commands, but do not expose their implementation or individual test coverage. We therefore cannot say which destinations the checks contacted or what they verified. No portfolio-by-portfolio browser evaluation accompanies this run, and the results do not establish that the hosted directory application works.

Browse before installing

You can read the Markdown directory in a browser. Local installation is unnecessary if your task is finding examples for your own portfolio.

Try a specific comparison: can a visitor identify the developer's contribution to a project without opening its source? For each shortlisted site, record where that explanation appears and whether the homepage makes it easy to find. Then compare that with a project description you have written yourself. These are suggested browsing steps; we did not execute this exercise or assess its results.

Before copying assets or code, check the destination's own permissions and license. Inclusion in a directory does not establish permission to reuse another person's writing, images or implementation.

Follow the contribution checklist with care

The contribution guide asks contributors to open their portfolio link, check that it loads without an error or parking redirect, add the entry in strict first-name order and leave feed.json unchanged because it is generated automatically.

The guide says a scheduled workflow checks links every Saturday and flags broken or parked destinations for removal. This is the documented policy. The supplied packet does not include the workflow implementation or a report proving that schedule completed, so it cannot establish current availability across the directory. Open a destination yourself before recommending it.

The longer Git guide needs caution. It refers to master in its maintenance steps, then says to create a branch off develop and elsewhere warns about staging. Those inconsistent references weaken its value as a command-by-command tutorial. Use the submission checklist to understand the required change and confirm the current target branch in GitHub before submitting. No contribution commands were executed for this review.

For repeatable research, record the checkout commit and retrieval date. Our measurements belong to 39bb80c; the supplied README and contribution extracts are not pinned to that commit. Release availability is unverified, so this review makes no claim that the repository has no releases.

Choose an alternative for a different next step

Portfolio Ideas includes screenshot and technology columns. Choose it when those details will help narrow your browsing. We did not verify the listed technologies against the destination implementations.

Awesome Portfolio Websites is a website project whose README presents experience, project and research pages. Choose it when you want a codebase to evaluate for adaptation. We did not test its installation or deployment.

How the ratings work

The editorial rubric uses 1 for substantial documented obstacles, 2 for a partial path with unresolved obstacles, 3 for a usable documented path with material limits, 4 for a straightforward path supported by documentation or the supplied run, and 5 for broad independent verification within the rated scope. These are editorial judgments, not benchmark scores. Missing evidence receives N/A.

Setup ease earns 4 because browser access needs no local installation and the supplied installation and build succeeded. Documentation earns 3 because the checklist is concrete but the longer guide mixes branch references. Community support and directory-wide maturity remain unassessed.

Before choosing a layout, write one project explanation in your own words. Use the directory to find a presentation that makes that explanation easy for your intended reader to reach.

Alternatives

ProjectWhat it isPick it when
Portfolio IdeasA portfolio reference collection with screenshot and technology columns.Choose it when previews and listed technologies will help you decide which examples to open. We did not test the linked sites or verify their listed stacks.
Awesome Portfolio WebsitesA community website project whose README presents experience, project and research pages.Choose it when your next task is evaluating a website codebase to adapt. Its README establishes the project format; we did not test setup or deployment.

Sources

  1. Developer Portfolios README
  2. Contribution guide and checklist
  3. Portfolio Ideas README
  4. Awesome Portfolio Websites README

More dev tools reviews