royalcms/wechat-js

The package has a very small artifact and minimal consumer documentation. Its organization-owned repository is not archived, but it has had no recent commits and no security policy, while the repository does not clearly identify this package.

Latest v5.0.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README, but it is only 20 characters long and provides almost no integration guidance. Missing tests and changelog files are normal for a published artifact and are not concerns here.

Release history

There has been only one release, published 2,578 days ago, with no releases in the last 12 months. That leaves substantial uncertainty about maintenance and compatibility.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the 2019 release date, this is meaningful evidence of likely abandonment.

Repo package mention

The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, the available evidence does not establish that relationship, so provenance is less clear.

Security policy

The repository has no security policy. This is a transparency and response-process gap, especially for a package with no recent visible maintenance.