Package Health

hasanhawary/media-manager

This release appears generally suitable to depend on: it is a stable 1.5.3 release, has a matching and package-referencing source repository, substantial documentation, comprehensive tests, an MIT license, no deprecation status, and a clean workflow risk profile. The main concerns are that the repository shows no commits or active maintainers in the last 3 months, has no security policy or security scanning, and its single workflow does not declare top-level token permissions. These are meaningful transparency and maintenance-process gaps, but they are offset by the recent release activity, the repository being unarchived, and the strong package structure and test coverage.

Latest 1.5.3PackagistPackagist

78%

Total Score

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

50

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

80

Health Score Breakdown

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing or redundancy for maintenance continuity.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers over the last 3 months, indicating a recent collapse in observed development activity despite the recent package release.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently negative, but it provides little evidence of an active maintenance or user-support process.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 0 watchers. This is weak supporting evidence, but low popularity alone does not make a small, otherwise coherent package unsafe.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning layer is a genuine security-process gap, though it is not itself evidence of malicious behavior.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Hasan Hawary

Direct Dependencies

DependencyLast ReleaseScore
illuminate/http
Version ^10.0 || ^11.0 || ^12.0 || ^13.0
—
—
league/flysystem
Version ^3.0
—
—
illuminate/config
Version ^10.0 || ^11.0 || ^12.0 || ^13.0
—
—
illuminate/support
Version ^10.0 || ^11.0 || ^12.0 || ^13.0
—
—
illuminate/container
Version ^10.0 || ^11.0 || ^12.0 || ^13.0
—
—

Weekly Downloads

Info

Last Published
28 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