bcmdevteam/bcm-crypt

Release historydanger

The package is about 10 years old but has only two releases, both from June 2016, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap.

Package file treecaution

The artifact and repository each contain only six files, including a very small implementation and no visible test or development structure. For a cryptography library, this provides limited evidence of maturity.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is not decisive, but these figures provide no supporting evidence of broader adoption or community oversight.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. The build tooling is appropriate, while the missing security checks are a modest transparency gap.