jiangwang/amis-schema

The MIT license, README, repository tests, and minimal runtime dependencies make adoption straightforward. Maintenance evidence is limited because there were no commits in the last three months and no published security policy.

Latest 1.0.3

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is about 13 months old with four releases, but only one release in the last 12 months and the latest release was about seven months before collection. This suggests a slow maintenance cadence rather than abandonment by itself.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. With the latest push also tied to the latest release, this limits confidence in ongoing maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers maturity confidence modestly but does not establish abandonment.

Repo tooling

Composer is used as a build tool, but no security scanning tools were detected. The missing scanning is a hygiene limitation, not a severe dependency risk on its own.

Security policy

The repository has no security policy. This reduces disclosure transparency, although it does not by itself show that the package is unsafe to depend on.