raxos/cache

Maintainerscaution

Only one registry account has publish access, which limits publishing redundancy. The package's active release history partly compensates, but it still indicates a thin operational base.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no provided evidence of broader organizational backing. This makes the single-maintainer concern more relevant.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Although frequent registry releases show recent publishing, the lack of observed source activity is a maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a library with frequent releases, this leaves a meaningful transparency and quality-control gap.

Security policycaution

The repository has no security policy. This does not make the package unsafe by itself, but it reduces transparency about vulnerability reporting and maintenance expectations.