ascetic-soft/waypoint

Documentation, tests, and release notes are present, and the organization-backed repository is clearly tied to the package. Workflow references are all unpinned, and the repository has no security policy or scanning, leaving build hygiene weaker than its package structure suggests.

Latest v1.2.1

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is young at about 217 days and made all 9 releases in a burst, with a median interval of about 4 hours. This shows active initial publishing but does not yet establish a durable maintenance pattern.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers during the last three months. For a package only about 217 days old, this is a meaningful indication that maintenance may have slowed or paused.

Repo tooling

The project uses Make and Composer, but no security scanning tools were detected. Build tooling is present, while the missing scanning coverage is a modest transparency and maintenance concern.

Security policy

No repository security policy was found. This weakens the project's documented process for receiving and handling vulnerabilities, though it is not evidence of an unsafe release by itself.

Workflow audit

The single workflow was fully analyzed, uses read-only permissions, and has no reported dangerous sinks or audit findings. However, all 7 action references are unpinned, leaving the build exposed to dependency movement over time.