itzmekhokan/sitecargo

Maintainerscaution

Only one registry account has publishing access, and the project backing is a personal repository. This leaves limited visible publishing redundancy, though access records alone do not establish maintenance quality.

Release historycaution

The package is about four months old and has only two releases, both published on the same day. That provides little evidence of an established release cadence.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last three months, while the latest push was about four months ago. This is a meaningful maintenance concern for an early package.

Repo toolingcaution

Composer is used as a build tool, but no security-scanning tool was detected. For a package handling WordPress content and media, that is a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This limits clarity about how vulnerabilities should be reported, though it is not by itself evidence that the package is unsafe.