dandisy/webcore

Documentation, tests, release notes, licensing, and a matching source repository provide useful transparency. The missing security policy and scanning reduce confidence, while the old release and absent recent commits make long-term maintenance uncertain.

Latest 1.0.8

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over 7 years ago, with no releases in the last 12 months. Nine releases show some history, but the prolonged release gap is a significant maintenance concern.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Its last push was in July 2023, so the repository is not abandoned administratively but has no recent development evidence.

Repo issue activity

There were no new or closed issues or pull requests in the last month, alongside four open issues and two open pull requests. This supports the broader picture of limited current project activity.

Repo tooling

Composer is used for builds, but no security-scanning tool was detected. The build setup is present, while the lack of automated security tooling modestly lowers assurance.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a Laravel platform with authentication and authorization components.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
doctrine/dbal Version ~2.3	—	—
laravel/tinker Version ~1.0	—	—
fideloper/proxy Version ~3.3	—	—
jlapp/swaggervel Version dev-master	—	—
laravel/passport Version ^4.0	—	—