derekdowling/stubborn

Tests, release notes, and a linked matching repository provide useful transparency. The license mismatch and lack of security tooling add maintenance uncertainty, so pinning this old release should be treated as a liability.

Latest 0.1.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in November 2014, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency handling external API calls.

Repo commit activity

The repository has zero commits and zero active maintainers in the last three months, while its last push was in December 2014. The long-standing inactivity materially raises abandonment risk.

License

The artifact contains a license file and the repository also has one, but the manifest declares MIT while the detected file is Apache-2.0. That mismatch should be clarified before adoption.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and two issues remain open. This supports the broader picture of an inactive project.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone severe risk.