ruwork/skolkovo-client

Release historydanger

Only two releases were published, with the latest over eight years ago and none in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Repo popularitycaution

The repository has zero stars and forks, with four watchers. Popularity is only supporting evidence, but these counts provide no meaningful community-maintenance buffer.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This is a transparency and maintenance gap, though it is secondary to the prolonged inactivity.

Security policycaution

The repository has no security policy, reducing guidance for reporting and handling vulnerabilities. The small, inactive project does not provide a compensating security process.