kyslik/django-bcrypt

Risky to adopt: the package has had no release or repository activity since March 2017, and its very small user and contributor footprint offers little evidence of ongoing support. It is licensed and has basic documentation, but appears effectively abandoned.

Latest 0.0.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in March 2017, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.

Repo commit activity

There were zero commits and zero active maintainers during the last three months, following the last repository push in 2017. This is the clearest indication that maintenance has stopped.

Project backing

The repository is owned by the matching individual registry namespace rather than an organization, so there is no organizational backing to offset the single-maintainer and inactivity concerns.

Repo issue activity

There are no open issues or pull requests, and no issue or pull-request activity in the last month. With no recent commits, this is consistent with an inactive project rather than a clearly healthy resolution process.

Repo popularity

The repository has only 1 star, 1 fork, and 1 watcher, providing little supporting evidence of community review or durable project backing.