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

applicable weight 80%

bayselonarrend/openintegrations

Language: 1C Enterprise
branch main
mirror

Набор инструментов интеграции с популярными сервисами и технологиями для 1С:Предприятие, OneScript и CLI+MCP (Telegram, VK, Bitrix24, Google, Яндекс, S3, PostgreSQL, SQLite, MySQL и др.)

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 6 October 2026 at 21:17 UTC — part unavailable

What the 100 is made of

category weight
Documentation 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 / weight
Documentation and best practicessignal coverage 78%
16.4–22 / 25
partial
Project activitysignal coverage 33%
7.7–24.4 / 25
partial
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
6.2 / 18.8
scored
Code health
0–12.5 / 12.5
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: tests directory, Dockerfile, 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
Not measured: commits in the last year, weekly activity, top author's share of commits, unique authors
data not collected
the surface didn't answer this collection run

Strengths

what's already done
  • The README introduces the project
  • Commits are fresh (2 days)
  • The license file is in place
  • Documentation has its own directory
  • A contributor guide is in place

What affected the score

Penalties

Documentation and best practices

  • −3
    dependency lockfilemissing
  • −<1
    share of short commit messages — 16%

Project activity

  • −1
    last release — 80 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −11
    age of open issues — 490 days50 issues
  • −1
    issue resolution time — 2 days50 issues

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
    tests directorydata not collected
  • up to −3
    Dockerfiledata not collected

Project activity

  • up to −4
    commits in the last yeardata not collected
  • up to −4
    weekly activitydata not collected
  • up to −4
    top author's share of commitsdata not collected
  • up to −4
    unique authorsdata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Issues
    +11
    work through the stale open issuesage of open issues — 490 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
    +9
    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
  • Documentation
    +3
    add a dependency lockfiledependency lockfilewhy: the build and the checks are reproducible for whoever takes the code
  • close issues faster+1
  • publish a release or tag a version+1
  • write meaningful commit messages+<1