dotfiles
Configuration couture
A dotfiles repository is the software equivalent of labeling every drawer in the house: wonderfully personal, endlessly refinable, and somehow still one misplaced alias away from a dramatic relocation.
Profiles, repos, scores & roasts
dotfiles
A dotfiles repository is the software equivalent of labeling every drawer in the house: wonderfully personal, endlessly refinable, and somehow still one misplaced alias away from a dramatic relocation.
Repository binding unavailable
A personal website repository is a noble digital front door—especially when it keeps its HTML credentials on display while quietly waiting for the next coat of paint.
Historical result · no repository binding was retained
dotfiles
Pairing dotfiles with a personal site says, “I will customize the terminal and the homepage before breakfast,” which is an impressively focused definition of a personal computing ecosystem.
Repository binding unavailable
The portfolio has achieved elegant minimalism: one repository for how the computer behaves and one for how the person appears online. The rest of the software universe can file a visitor request.
Historical result · no repository binding was retained
Impact
25% weight
The portfolio includes personal configuration and a personal website, both useful project types, but the available scope appears limited.
Consistency
15% weight
Two owned repositories show activity in 2021, but the supplied metadata does not show more recent contribution patterns.
Quality
25% weight
Both repositories are original rather than forks and are not marked archived; metadata alone provides only modest engineering-maturity evidence.
Depth
20% weight
Maintaining both a dotfiles repository and a personal website suggests some sustained ownership, though the supplied dates and repository count indicate limited visible depth.
Breadth
10% weight
The portfolio spans Shell and HTML, but only two closely personal project categories are represented.
Community
5% weight
The available community signal is neutral-to-moderate, with 40 followers; popularity is not used to raise or lower the other categories.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
2
Last 12 months
0
Accepted fact
40
Profile date
Apr 2009
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
jamesmackinnon /
38/100
An original Shell dotfiles repository, active through 2021 and apparently maintained as a personal configuration project; its supplied metadata supports ownership but not deeper implementation or quality conclusions.
jamesmackinnon /
36/100
An original HTML personal-site repository, active through 2021 and not archived; it represents a coherent personal publishing project, with limited scope visible from the available metadata.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 32 | 8.00 |
| Quality | 25% | 40 | 10.00 |
| Depth | 20% | 30 | 6.00 |
| Consistency | 15% | 35 | 5.25 |
| Breadth | 10% | 28 | 2.80 |
| Community | 5% | 50 | 2.50 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for jamesmackinnon. The portfolio includes personal configuration and a personal website, both useful project types, but the available scope appears limited.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for jamesmackinnon. Both repositories are original rather than forks and are not marked archived; metadata alone provides only modest engineering-maturity evidence.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for jamesmackinnon. Maintaining both a dotfiles repository and a personal website suggests some sustained ownership, though the supplied dates and repository count indicate limited visible depth.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for jamesmackinnon. Two owned repositories show activity in 2021, but the supplied metadata does not show more recent contribution patterns.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for jamesmackinnon. The portfolio spans Shell and HTML, but only two closely personal project categories are represented.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for jamesmackinnon. The available community signal is neutral-to-moderate, with 40 followers; popularity is not used to raise or lower the other categories.
Validate. The server validates the login, signed browser session, attempts, cooldown, daily ceiling, and the single provider permit.
Collect. The VPS collector reads bounded public profile metadata and up to 12 recent repository metadata rows in volatile memory.
Rate. One pinned provider returned a closed profile-rating object with no tools, browsing, shell, or repository-content access.
Verify. Server checks bound the subject, rejected unsafe or echoed text, validated the schema, and recomputed rubric-v3 final arithmetic.
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