juteexj/sayhi-saybye

The repository is tiny and has no security policy or automated security scanning. The package is stable and has no install-time scripts, but its maintenance and licensing gaps make long-term dependency use risky.

Latest v1.0.1

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

License

The package declares no license, contains no license file, and the linked repository also has no license file. That leaves the legal terms for dependency use unclear.

Release history

There has been only one release, published over seven years ago, with no releases in the last 12 months. This strongly limits evidence of ongoing maintenance.

Repo commit activity

The repository has no commits or active maintainers in the last three months, consistent with the last push occurring over seven years ago. This is substantial evidence of abandonment risk.

Package file tree

The artifact and repository each contain only three files: two executable-looking entries and composer.json. This matches the publisher's minimal test-bin description, but provides very little supporting project structure.

Package scaffolding

The artifact has no README, tests, or changelog, and the repository reports none either. For this very small package the missing tests and changelog are less significant, but the missing README still reduces transparency for consumers.