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

applicable weight 65%

mezentsevs/virtual-file-system

Language: Vue
branch main

🗂️ A full-stack SPA implementing a virtual file system with a hierarchical tree structure. It supports full CRUD operations, validation, and sorting, providing an intuitive interface for managing files and folders directly in the browser. Built with PHP, Laravel, MySQL, JS, Inertia.js, Vue, Tailwindcss, Docker.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 18:49 UTC — part unavailable

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; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 76%
18.9–26.2 / 30.8
partial
Project activity
17.6 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–11.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
0–15.4 / 15.4
collection failed
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
Not measured: docs directory, Dockerfile, contributing guide, TODO/FIXME density
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it

Strengths

what's already done
  • The README introduces the project
  • Work goes on without long pauses (8 weeks)
  • Commits span the whole year (19 commits)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −3
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 12%

Project activity

  • −5
    last release — 586 days
  • −3
    top author's share of commits — 89%
  • −3
    unique authors — 2 authors
  • −2
    last commit — 134 days
  • −<1
    commits in the last year — 19 commits

CI/CD

  • −12
    SourceCraft CI configurationmissing

Not measured — interval width

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

Documentation and best practices

  • up to −3
    docs directorydata not collected
  • up to −3
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −12
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +12
    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
    publish a release or tag a versionlast release — 586 dayswhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +3
    share the work with other contributorstop author's share of commits — 89%why: the work does not rest on a single person
  • set up a review policy+3
  • bring in a second maintainer+3
  • make a commit soon+2
  • set up a branch protection policy+1
  • commit more often+<1
  • write meaningful commit messages+<1