Skip to the main content
The Repo Vitals mark: a pulse that ends in a commitREPO VITALS

applicable weight 70%

a13xp0p0v/linux-kernel-defence-map

branch master
mirror

Linux Kernel Defence Map shows the relationships between vulnerability classes, exploitation techniques, bug detection mechanisms, and defence technologies

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 70%analysed 2 October 2026 at 21:15 UTC — not all categories measured

What the 100 is made of

category weight
Documentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10

The light segments — Security: will appear with a member token; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
10.3 / 28.6
scored
Project activity
13.3 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–10.7 / 21.4
partial
Issues
5 / 21.4
scored
Code health
no data
States:
scored
partial
no data
weight goes to the rest
collection failed
interval, not zero
Not measured: CI runs
closed by the platform
will become a group once access opens

Strengths

what's already done
  • The license file is in place
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

  • −4
    README3,630 chars, no quickstart
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −2
    contributing guidemissing
  • −<1
    share of short commit messages — 10%

Project activity

  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −2
    weekly activity — 2 weeks
  • −1
    last commit — 137 days
  • −1
    last release — 137 days
  • −1
    commits in the last year — 16 commits

CI/CD

  • −11
    SourceCraft CI configurationmissing

Issues

  • −14
    age of open issues — 1,259 days6 issues
  • −2
    issue resolution time — 5 days6 issues

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

CI/CD

  • up to −11
    CI runsdata not collected

What will raise the score

by strength of impact
  • Issues
    +14
    work through the stale open issuesage of open issues — 1,259 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • CI/CD
    +11
    add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CISourceCraft CI configurationwhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +5
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • bring in a second maintainer+5
  • add a quickstart section to the README+4
  • write tests for the project+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • spread work across more weeks instead of bursts+2
  • close issues faster+2
  • add a contributing guide+2
  • make a commit soon+1
  • publish a release or tag a version+1
  • commit more often+1
  • write meaningful commit messages+<1