Package Health/silverbullet/api-token-laravel

silverbullet/api-token-laravel

Its MIT license, direct package-to-repository match, and minimal dependency surface reduce adoption friction. The README is usable, but the project has no recent development and no security scanning.

Latest 1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The last release was about 5 years and 6 months ago, with no releases in the past 12 months. The 13 releases were concentrated near the project's start, indicating likely abandonment.

Repo commit activity

There were no commits and no active maintainers in the past 3 months, consistent with the release gap and creating substantial abandonment risk.

Project backing

The repository is owned by an individual account rather than an organization, providing limited visible organizational backing for a package published under the silverbullet namespace.

Repo popularity

The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is not decisive, but this provides little evidence of a broader support community.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This weakens ongoing security and maintenance assurance for a package handling API authentication.