marussia/config

Release historydanger

Only two releases were published, with the latest in October 2019 and none in the last 12 months. This long period without releases is strong evidence of abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive since October 2019.

Package scaffoldingcaution

The package includes a README and this version has a GitHub release, but the README is only 8 characters and the repository has no tests or changelog. Missing tests and changelog are normal packaging practice, while the minimal README limits consumer guidance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, indicating very limited adoption or external validation. Popularity is supporting evidence rather than a verdict, but it reinforces the maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool is configured. The missing scanner is a modest transparency and maintenance gap for a dependency package.