panoscape/assets

Release historydanger

Only one release exists, published nearly ten years ago, with no releases in the last 12 months; this is strong evidence of abandonment for a Laravel library.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long-standing lack of releases.

Maintainerscaution

One registry maintainer is a thin publishing base; the linked repository is user-owned, so there is no organization backing shown to compensate for that concentration.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported, which provides little evidence of ongoing dependency or code-security maintenance.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this adds a transparency gap to an already inactive project.