flynn314/pint

Release historydanger

The package has had 10 releases, but none in the last 12 months; its latest release was about 18 months ago. This indicates a substantial maintenance gap.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, reinforcing the evidence that development has stopped.

Package file treecaution

The artifact and repository each contain only composer.json and pint.json, leaving very little source or documentation to establish maturity and long-term support.

Package scaffoldingcaution

The published artifact has no README, which makes a package consumers must configure harder to understand. Missing tests and changelog files are normal for published artifacts and do not independently lower health here.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected; this is a modest hygiene gap for a dependency package.