kavience/ruyicmf-api

Apache-2.0 licensing and a single runtime dependency make the package straightforward to inspect and integrate. The repository has no security scanning or policy, leaving limited evidence of ongoing safeguards.

Latest 6.0.1

Packagist

39%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in September 2023, with no releases in the last three years. This indicates a largely inactive release process for a maintained API dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the roughly three-year gap since its last push.

Package scaffolding

The artifact has no README, which makes an API package harder for consumers to understand and integrate. The absence of tests and a changelog is not counted as a gap because those belong in the source project or may not be published in the artifact.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. That leaves less evidence that dependency or source risks are checked automatically.

Security policy

The linked repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a maintenance and transparency gap, though not evidence of malicious behavior.