existenznl/permcheck

Project backingcaution

The repository is owned by a user account rather than an organization, so the single registry maintainer provides limited visible backing capacity.

Release historycaution

The package has 12 releases since January 2016, but none in the last four years; the long release gap raises abandonment risk despite its established history.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, weakening evidence of ongoing maintenance and partially offsetting the repository's recent push timestamp.

Security policycaution

The repository has no security policy, so reporting and response expectations are not documented; this is a transparency gap, though not a severe dependency risk by itself.

Workflow auditcaution

The single workflow was fully analyzed with no audit findings or untrusted checkout, injection, or broad write permission issues. However, all three action references are unpinned, leaving avoidable build reproducibility risk.