casemark/casedev

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, despite a recent push timestamp. For a package with frequent releases, this is a meaningful concern that releases may be automated or maintenance may have paused.

Repo issue activitycaution

There were two new pull requests in the last month but none merged and no issue activity, indicating some engagement without demonstrated resolution. This is a mild maintenance concern rather than evidence of abandonment.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no community adoption signal. Popularity is only supporting evidence, so this lowers confidence more than health on its own.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces repository hygiene and transparency, although it is not by itself evidence that the package is unsafe.

Token permissionscaution

All five workflows omit top-level token permissions, and none declares read-only permissions; one uses job-level permissions only. This leaves workflow privileges less explicit than desirable and creates a repository hygiene concern.