brainsum/dropzone

Release historydanger

The latest release was published in March 2020, with no releases in the last 12 months; this is a substantial abandonment concern for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the release history and indicating that maintenance has stopped.

Maintainerscaution

Only one registry account has publish access, which is a thin publishing base. The organization-owned repository provides some backing, so this is a limited concern rather than a severe one.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance-hygiene gap, not evidence of maliciousness.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities. This matters more for an actively maintained dependency, but still reduces transparency.