Package Health

brikocode/framework

The complete README, MIT licensing, and package-to-repository match improve transparency. Missing security scanning, unpinned workflow actions, and a very small project footprint leave meaningful maintenance and build-hygiene concerns.

Latest v0.4.0PackagistPackagist

54%

Total Score

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

25

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

75

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

67

Health Score Breakdown

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, a concrete sign that ongoing maintenance may have slowed or stopped.

Maintainerscaution

Only one registry maintainer is listed, which gives the release a thin publishing base; the individual-owned repository provides no evidence of a broader organization-backed team.

Release historycaution

Four releases arrived within roughly one day, showing active initial publishing but too little history to demonstrate sustained maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but popularity alone does not determine whether a small package is healthy.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling was detected, leaving automated vulnerability checking uncovered.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Brikocode

Direct Dependencies

No direct dependencies.

Weekly Downloads

Info

Last Published
5 months ago
Created
5 months 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