Package Health

agentsib/crypto-bundle

This release appears usable and reasonably healthy: it is a stable v4.0.0 release, is not deprecated, has a valid MIT license, includes a substantial file tree with both unit and functional tests, and was published very recently. The main concerns are that repository commit activity shows no commits or active maintainers in the last 3 months, the project has only three stars and three forks, there is no security policy or security-scanning tooling, and publishing access is concentrated in one account. These issues suggest limited maintenance capacity and transparency, but they are outweighed by the recent release, active non-archived repository, coherent package/repository match, and strong test scaffolding.

Latest v4.0.0PackagistPackagist

72%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

63

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

90

Health Score Breakdown

Maintainerscaution

Only one account has registry publish access. This is a maintenance-capacity concern, although registry access alone does not establish who actively maintains the project.

Project backingcaution

The source repository is owned by a user account rather than an organization. This provides less institutional backing and makes the single-maintainer concern more material.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Despite the recent release and push, the absence of recent commit activity raises a genuine maintenance-capacity concern.

Repo popularitycaution

The repository has only 3 stars, 3 forks, and 1 watcher. Low popularity is supporting caution about external validation, but it is not decisive for a small, coherent package.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning layer reduces security-process transparency for a package handling cryptographic functionality.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Ilya Kovalenko

Direct Dependencies

DependencyLast ReleaseScore
doctrine/orm
Version ^2.17 || ^3.0
—
—
symfony/yaml
Version ^6.4 || ^7.0
—
—
doctrine/persistence
Version ^3.0 || ^4
—
—
doctrine/doctrine-bundle
Version ^2.13 || ^3.0
—
—
symfony/framework-bundle
Version ^6.4 || ^7.0
—
—

Weekly Downloads

Info

Last Published
25 days ago
Created
4 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform