t4g/kit-exception

The source is minimal and gives consumers no README or tests to guide integration. Its MIT declaration, simple dependency profile, and absence of install scripts are reassuring, but the long inactivity makes a new dependency risky.

Latest 1.0.0

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository contain no README, while the repository also has no tests or changelog. Missing tests and changelog are not unusual for a small published artifact, but the absent README leaves consumers without integration guidance.

Project backing

The repository owner is an individual account rather than an organization. That does not prove weak backing, but there is no organizational support signal to compensate for the lack of recent activity.

Release history

This package has only one release, published about 12 years and 10 months ago, with no releases in the last 12 months. That strongly suggests abandonment risk despite the stable 1.0.0 version.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher, providing little evidence of an active user or contributor community. Small packages can still be healthy, but this does not compensate for the long inactivity.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a minor transparency gap rather than a decisive concern for this very small package.