edulazaro/astronomy

The package includes a substantial README, tests, matching MIT licensing, and minimal runtime dependencies. Its repository and release history are too short to demonstrate long-term maintenance, while the workflow still relies on unpinned actions.

Latest 1.0.1

Packagist

73%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 0 days old with two releases about 80 minutes apart, so there is not yet enough history to establish a durable maintenance pattern. This reflects limited evidence rather than abandonment.

Repo commit activity

There were zero commits and zero active maintainers in the three-month activity window. Because the repository is newly created and was pushed recently, this mainly leaves maintenance capacity unproven rather than showing clear abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap, not evidence that the release is unsafe by itself.

Security policy

The repository has no security policy. For a newly published, user-owned project this weakens vulnerability-reporting transparency, though it does not establish a maintenance failure on its own.

Workflow audit

The single workflow was fully analyzed, uses read-only permissions, and has no untrusted checkout or injection findings. However, all 4 action references are unpinned, leaving build inputs less reproducible and harder to control.