wesleydeveloper/data-processor

Release historydanger

The package has four releases, but none in the last 12 months despite being about 14 months old. Its releases were concentrated within about 53 minutes, providing little evidence of sustained maintenance.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with no releases in the last year, this is strong evidence that maintenance has stalled.

Maintainerscaution

Only one registry account has publish access. This is a thin publishing base for an independently owned project and increases continuity risk if that maintainer becomes inactive.

Project backingcaution

The repository is owned by an individual user rather than an organization, and the registry and repository owners match. The ownership is transparent but offers no organizational maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, though it is less significant than the inactivity evidence.