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

applicable weight 65%

flexberry/ember-flexberry

Language: JavaScript
branch develop
mirror

Ember Flexberry Addon - SPA Framework powered by Ember.js

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 19:16 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 72%
22.2–30.8 / 30.8
partial
Project activitysignal coverage 83%
17.9–23 / 30.8
partial
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, last release, 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
  • The license file is in place
  • Tests live in the repository
  • Dependency versions are pinned
  • Commit messages are meaningful

What affected the score

Penalties

Project activity

  • −3
    last commit — 204 days
  • −2
    top author's share of commits — 71%
  • −2
    commits in the last year — 7 commits
  • −1
    unique authors — 3 authors
  • −1
    weekly activity — 5 weeks

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 −2
    contributing guidedata not collected

Project activity

  • up to −5
    last releasedata 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
    +3
    make a commit soonlast commit — 204 dayswhy: the repository shows it is alive, not abandoned
  • Activity
    +2
    share the work with other contributorstop author's share of commits — 71%why: the work does not rest on a single person
  • commit more often+2
  • bring in a second maintainer+1
  • spread work across more weeks instead of bursts+1