jiny/site-board

The package includes a substantial source tree, documentation, and an MIT declaration, with no install-time scripts. Its single publisher and lack of security scanning or policy leave limited independent oversight.

Latest 0.7

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access, which limits visible release coverage. The organization-owned repository provides some backing, so this is a limited concern rather than a severe risk.

Release history

The package has had no releases in the last 12 months, and the latest release was about 19 months ago. Its seven releases and roughly monthly earlier cadence provide some maturity, but current maintenance appears stalled.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, reinforcing the long gap since the latest release. The repository is not archived, but there is no recent development evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is useful, while the missing security automation modestly reduces transparency and assurance.

Security policy

The linked repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This matters for a Laravel package that handles application and database-facing functionality.