ernestdefoe/reel

Maintainerscaution

One registry maintainer is responsible for publishing the package. That is workable for a small extension, but it leaves limited visible redundancy if the maintainer becomes unavailable.

Release historycaution

This is the package's first release, published today, so there is no track record yet for maintenance or release reliability. Its newness explains the gap but does not remove the uncertainty.

Repo commit activitycaution

The repository has no commits in the last three months and no active maintainers in that period. Because the repository was created and released today, this is limited evidence rather than proof of abandonment.

Security policycaution

The repository has no published security policy. This is a transparency and reporting gap, though it is not by itself evidence that the package is unsafe.

Workflow auditcaution

Both workflows were analyzed without untrusted triggers, injection findings, or audit failures, but one workflow grants top-level write permissions. That is a mild workflow-hygiene concern because the token scope is broader than necessary.