Package Health

moonshine/core

This release appears suitable for dependency use and is supported by a healthy release cadence, stable versioning, a non-deprecated registry status, an active unarchived organization-owned repository, clear licensing, and a package tree that matches the linked project. The main concerns are concentrated recent development in one contributor, no repository security policy or security scanning, no tests or changelog in the collected artifact/repository, and very low repository popularity; these reduce resilience and transparency but do not outweigh the evidence of ongoing maintenance and organizational backing.

Latest 4.18.2PackagistPackagist

78%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

70

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

90

Health Score Breakdown

Maintainerscaution

Only one registry account has publish access, which is a concentration concern in isolation. The linked repository is organization-owned, providing some backing, but registry publishing remains dependent on one account.

Repo bus factorcaution

All 5 recent commits came from one contributor, creating a genuine continuity risk. Organization ownership provides some ability to hand maintenance off, but no second active contributor is shown in this signal.

Repo issue activitycaution

There were no new or merged pull requests and no new or closed issues in the last month, which gives limited evidence of community activity. This is softened by the separate evidence of recent commits and regular releases.

Repo popularitycaution

The repository reports zero stars and forks and only one watcher, so there is little public adoption evidence. Popularity is supporting evidence rather than a verdict, and the maintenance signals compensate for much of this gap.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The build setup is appropriate, while the missing security automation is a hygiene gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Danil Shutsky

Direct Dependencies

DependencyLast ReleaseScore
psr/container
Version ^2.0
—
—
psr/http-message
Version ^2.0
—
—
psr/simple-cache
Version ^3.0
—
—
moonshine/support
Version ^4.0
—
—
illuminate/support
Version ^10|^11|^12|^13
—
—

Weekly Downloads

Info

Last Published
2 months ago
Created
2 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform