tgraboski/tarjan

The package is licensed and has no install-time scripts, but its documentation is only a title and the project has no tests or security policy. Pinning this release leaves you dependent on a project with no release or commit activity for roughly nine years.

Latest 1.0.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published roughly 10 years and 7 months ago, with no releases in the last 12 months. That is strong evidence of abandonment, although the package is small and simple.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the roughly nine-year gap since the last repository push. This materially increases abandonment risk.

Package scaffolding

The artifact includes a README, but it is only 8 characters long and contains the title, offering almost no integration guidance. Missing tests and changelog files are normal for published package artifacts and are not counted as gaps here.

Project backing

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the single-maintainer and inactive-project concerns.

Repo tooling

Composer is used for the build, which is appropriate for this package, but no security scanning tooling is present. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.