jerfeson/slashtrace

The MIT license, substantial README, and broad test suite provide useful adoption and maintenance context. Missing security policy and security scanning leave operational safeguards unclear.

Latest 1.0.0

Packagist

45%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, 1.0.0, published over three years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable version.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but current maintenance activity is absent.

Repo issue activity

There were no new or merged pull requests and no new or closed issues in the last month. This adds to the picture of an inactive project, although the open issue count is unknown.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The build setup is a modest positive, while the lack of automated security checks weakens maintenance confidence.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself show that the package is unsafe.