applicable weight 80%
ss-zlobin/taskmanager
Language: Python
branch main
TaskManager — это система оркестрации задач, похожая на Apache Airflow, но с упрощённой архитектурой. Поддерживает асинхронное выполнение, расписания и кастомные триггеры
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 30 September 2026 at 21:04 UTC — not all categories measured
What the 100 is made of
category weightDocumentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10
The light segment — Security: will appear with a member token, while the rest share its weight for now.
Six categories
earned / weightDocumentation and best practices10.7 / 25
scored
Project activity19.4 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%0–9.4 / 18.8
partial
Issues6.9 / 18.8
scored
Code health12.5 / 12.5
scored
States:weight goes to the restinterval, not zero
scored
partial
no data
collection failed
Not measured: CI runswill become a group once access opens
closed by the platform
Strengths
what's already done- Almost no marked debt in the code
- The README introduces the project
- Commits are fresh (8 days)
- Commits span the whole year (84 commits)
- Work goes on without long pauses (8 weeks)
What affected the score
Penalties
Documentation and best practices
- −2license filemissing
- −2docs directorymissing
- −2Dockerfilemissing
- −2dependency lockfilemissing
- −2review policyno protection
- −1contributing guidemissing
- −1branch protection policyno protection
- −<1share of short commit messages — 4%
Project activity
- −4last releaseno releases or version tags
- −1unique authors — 3 authors
- −1top author's share of commits — 57%
CI/CD
- −9SourceCraft CI configurationmissing
Issues
- −12age of open issues — 337 days1 issue
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 −9CI runsdata not collected
What will raise the score
by strength of impact- work through the stale open issuesage of open issues — 337 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026+12Issues
- 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+9CI/CD
- publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code+4Activity
- add a license file+2
- write project documentation+2
- containerize the project — add a Dockerfile+2
- add a dependency lockfile+2
- set up a review policy+2
- add a contributing guide+1
- set up a branch protection policy+1
- bring in a second maintainer+1
- share the work with other contributors+1
- write meaningful commit messages+<1