check-error

Release historycaution

The package is over 10 years old and has released once in the last 12 months, with the latest release about 8 months ago. Its limited release count suggests a small, infrequently changing project, though the recent release provides evidence it is not abandoned.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last 3 months. That is a meaningful maintenance concern, although the recent release and non-archived status provide some compensation.

Repo toolingcaution

No build tool or security scanning tool is detected in the repository. For a small JavaScript utility this is a hygiene gap rather than evidence of immediate unfitness, but it reduces confidence in ongoing maintenance controls.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a documentation gap rather than a standalone reason to reject the package.

Token permissionscaution

Both analyzed workflows lack top-level token permissions, and neither declares read-only permissions. One workflow has job-level permissions only, leaving the repository with weaker-than-desirable explicit CI permission boundaries.