Package Health

rajurayhan/larastreamer

Larastreamer v3.0.0 appears usable and reasonably transparent: it has an MIT license, a substantial README and changelog, a matching public repository with tests, CI tooling, and no install-time lifecycle scripts. However, the package has only two releases across roughly seven years, commit activity was absent during the last three months, and registry publishing is controlled by one maintainer. The repository is not archived and has a recent release, but the thin release history and recent inactivity create meaningful maintenance risk; missing security scanning, a security policy, and explicit workflow token permissions further reduce assurance. This is a viable dependency with monitoring, rather than a clearly mature low-risk choice.

Latest v3.0.0PackagistPackagist

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

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Maintainerscaution

A single registry maintainer creates a limited publishing and continuity base; the individual-owned repository provides no organizational backing to compensate for that concentration.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no demonstrated institutional backing to mitigate the package's single-maintainer and low-activity risks.

Release historycaution

Only two releases exist over approximately seven years, with one release in the last 12 months; the recent release is positive, but the unusually sparse history limits evidence of sustained maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers over the last three months. Although a recent release and merged pull request provide some compensating evidence, the recent development inactivity remains a maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; the missing scanning reduces assurance without independently making the package unfit.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Raju Rayhan

Direct Dependencies

DependencyLast ReleaseScore
illuminate/http
Version ^12.0 || ^13.0
—
—
illuminate/view
Version ^12.0 || ^13.0
—
—
illuminate/routing
Version ^12.0 || ^13.0
—
—
illuminate/support
Version ^12.0 || ^13.0
—
—
illuminate/contracts
Version ^12.0 || ^13.0
—
—

Weekly Downloads

Info

Last Published
27 days ago
Created
7 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