openjournalsoftware/bibtex

Release historydanger

This package has only one release, published more than 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with the repository's last push being more than 10 years ago. This is the clearest maintenance risk.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. A clean tracker can be benign, but here it provides no evidence of an active support community.

Repo popularitycaution

The repository has 1 star and 2 forks, indicating little community adoption or visible review. Popularity is supporting evidence, so this is a modest concern rather than a verdict.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap, not the main adoption risk.