furikus/sfera

Its MIT declaration and lack of install scripts are positives. The repository has no security policy or security scanning, so adopting it carries avoidable transparency risk.

Latest v0.0.1

Packagist

38%

Total Score

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The artifact and linked repository each contain only composer.json, with no implementation files visible. That is unusually thin for a package described as sending logs to multiple destinations and makes the release difficult to assess.

Release history

This release was published about 20 months ago, and it is the package's only release; there have been no releases in the last 12 months. That provides little evidence of active maintenance.

Package scaffolding

The package has no README, while tests and a changelog being absent are normal for a published artifact. Missing consumer documentation is still a meaningful gap for a library with multiple integrations.

Repo package mention

The linked repository is named artefact rather than sfera, and the collected data does not show the package name in its README. The repository may not actually be the source for this package.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures offer no external evidence of adoption or review.