Package Health

bnine/filesbundle

This is a usable, actively maintained release with a stable major version, 13 releases in the last 12 months, a non-archived repository, and recent commit activity. However, maintenance is concentrated entirely in one contributor, the repository has no tests, changelog, security policy, or security scanning, and the project has no observed community activity or adoption signals. The package is not deprecated and has a clear MIT declaration, so it is not unfit to depend on, but adopters should account for limited bus factor and modest transparency, especially for a file-upload and storage component.

Latest v1.4.4PackagistPackagist

68%

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

83

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

75

Health Score Breakdown

Maintainerscaution

Only one registry account has publish access. This is not decisive by itself because registry access lists do not measure actual maintenance, but it is consistent with the repository's single-contributor risk.

Package scaffoldingcaution

A substantial README documents installation, routes, and usage, but neither the artifact nor repository contains tests or a changelog. For a framework bundle handling uploads and file operations, the absence of repository tests is a meaningful maintenance and regression-risk gap.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing to compensate for the concentrated contributor base.

Repo bus factorcaution

All 16 commits in the last 3 months came from one contributor, with a 100% top-contributor share. This creates a genuine continuity and response risk for adopters.

Repo popularitycaution

The repository has zero stars, forks, and watchers, so there is no observed community adoption or external validation. Popularity is supporting evidence rather than a verdict, but this leaves the package's durability less demonstrated.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

afornerot

Direct Dependencies

DependencyLast ReleaseScore
imagine/imagine
Version ^1.0
league/flysystem
Version ^3.0
league/flysystem-bundle
Version ^3.0
symfony/framework-bundle
Version ^7.1
league/flysystem-aws-s3-v3
Version ^3.0

Weekly Downloads

Info

Last Published
17 days ago
Created
1 year 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