joshbrw/type-enforcement

The package includes a README, tests, MIT licensing, and no install-time scripts. Its tiny dependency surface helps, but the repository does not clearly identify this package and offers no security policy, reducing confidence in long-term support.

Latest v0.1.2

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than eight years, with only three releases overall and none in the last 12 months. This is strong evidence of abandonment risk despite the package not being formally deprecated.

Project backing

The package and repository are owned by the same individual account, so the ownership relationship is clear, but there is no organizational backing to compensate for a single-person project going inactive.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. Combined with the old last push, this is consistent with an inactive project.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That makes package-to-source identity unclear, even though the file tree is consistent with a small library.

Repo popularity

The repository has zero stars, forks, and watchers, providing no supporting evidence of community adoption. Popularity is only supporting evidence, so this reinforces rather than determines the maintenance concern.