aporteweb/dashboard

Release historydanger

Only one release exists, published nearly six years ago, with no releases in the last 12 months. This is strong evidence of a stale dependency and is not offset by the repository's current non-archived status.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed recently, the observed commit activity indicates no demonstrated ongoing maintenance.

Licensecaution

The package has no declared license, license file, or repository license file. That creates a material adoption and transparency problem for an open-source dependency.

Maintainerscaution

Only one registry account has publish access, which is a resilience concern. The organization-owned repository provides some compensating backing, so this is not treated as a severe risk by itself.

Repo toolingcaution

The repository uses Composer for builds, but no security scanning tooling was detected. This is a hygiene gap that adds some transparency risk alongside the older release.