guava/filament-nested-resources

This package is abandoned

The maintainer has marked guava/filament-nested-resources abandoned on Packagist; it should not be expected to receive fixes, and all its scores are set to 0. The maintainer did not suggest a replacement.

Score capped by active vetoes

  • maintenance.abandoned-flag — every category score set to 0
0 /100 0 Poor

Last checked 23 hours ago · results last changed 3 weeks ago

Repository
Security 55%
0 Poor
Maintenance 30%
0 Poor
Ecosystem 15%
0 Poor

Check details

Maintenance

Checks whether the maintainer has marked the package abandoned on Packagist or archived its repository. Marked abandoned on Packagist. No suggested replacement.

This veto is active: the check failed, so every category score is set to 0/100. Learn how scoring works.

Archived on
none
Repository archived
No
Marked abandoned on Packagist
Yes
Suggested replacement
none
Sources consulted
  • packagist
How this check works

A maintainer can tell the world that a package will not receive further fixes in two places: by marking it abandoned on Packagist, optionally naming a replacement, or by archiving the repository on the source host. Either one is the maintainer's own statement that future fixes will not come. That is the strongest warning a package can carry short of being malicious, and no amount of recent activity elsewhere changes it.

Plumb reads the abandoned flag from Packagist and the archived flag from the repository. Maintainers often set one without the other, so either one alone is enough. For a package that is not listed on public Packagist, the archived flag is the only signal available.

The check passes when neither flag is set and fails when either is. Failing sets every category score and the composite score to 0. When Packagist already carries the abandoned flag, the scan stops at this check, because nothing the other checks measure could change the outcome. When the maintainer named a replacement package, it is included in the evidence so the package page, the API, and the Composer plugin can point people to it.

How to improve this

Add a Plumb badge to your README. Displaying scores on your own site instead? See the API usage guidelines for attribution requirements.

Composite Score Plumb score
[![Plumb score](https://plumbphp.dev/badges/guava/filament-nested-resources/composite.svg)](https://plumbphp.dev/guava/filament-nested-resources)
Security Plumb security score
[![Plumb security score](https://plumbphp.dev/badges/guava/filament-nested-resources/security.svg)](https://plumbphp.dev/guava/filament-nested-resources)
Maintenance Plumb maintenance score
[![Plumb maintenance score](https://plumbphp.dev/badges/guava/filament-nested-resources/maintenance.svg)](https://plumbphp.dev/guava/filament-nested-resources)
Ecosystem Plumb ecosystem score
[![Plumb ecosystem score](https://plumbphp.dev/badges/guava/filament-nested-resources/ecosystem.svg)](https://plumbphp.dev/guava/filament-nested-resources)
Scanned Scanned by Plumb
[![Scanned by Plumb](https://plumbphp.dev/badges/guava/filament-nested-resources/scanned.svg)](https://plumbphp.dev/guava/filament-nested-resources)