graze/csv-token

It includes a clear MIT license, tests, a changelog, release notes, and a matching organization-owned repository. Its tiny dependency footprint and clean package layout reduce adoption friction, but no security policy is present.

Latest 0.3.1

Packagist

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about 10 years, with six releases total and none in the last 12 months. This is a substantial maintenance concern, although the package is not marked deprecated and the release is documented.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a dormant project, though it does not by itself show unresolved defects.

Repo tooling

The project uses Make and Composer for builds, which supports reproducible project tasks. No security scanning tools were detected, leaving a minor maintenance-hygiene gap.

Repository archived

The repository is not archived, which preserves a basic path for future maintenance, but it was last pushed about 10 years ago and therefore provides little evidence of current activity.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, but it is a moderate hygiene gap rather than evidence that the release is unsafe.