james-n-m/faker-pokemon

Release historydanger

The package has only one release, 1.0.0, published over six years ago, with no releases in the last 12 months. This is substantial evidence of inactivity, although the package may be intentionally small and stable.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the single-release history, this indicates an inactive project rather than merely a quiet release period.

Project backingcaution

The repository is owned by an individual user rather than an organization. The single registry maintainer is therefore consistent with the project backing, but it also indicates limited visible ownership depth.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. This avoids an unresolved backlog but also provides no evidence of active maintenance.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. The missing scanner is a hygiene gap, not evidence that the package is unsafe.