reva2/config-service-provider

Release historydanger

The latest release was about 10 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment despite the package having 10 total releases.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long release gap. This materially raises abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This is a modest repository hygiene gap, not evidence of malicious behavior.

Repository archivedcaution

The repository is not marked archived, but its last push was about 10 years ago. The non-archived status does not compensate for the observed inactivity.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. For an otherwise inactive project, that gap is more consequential.