tregor/proxyman

Release historydanger

The latest release was in June 2020, with no releases in the last 12 months and only four releases overall. This long period without publication is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release hiatus and leaving no evidence of current maintenance.

Maintainerscaution

Only one registry maintainer is listed, so the project has a thin publishing base. The repository is user-owned rather than organization-backed, providing no shown redundancy to offset that risk.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. This is a maintenance and transparency gap, though it is less significant than the absence of recent activity.

Security policycaution

The linked repository has no security policy, reducing transparency about how vulnerabilities would be reported and handled. No other provided signal compensates for this gap.