tuupke/laravel-swagger

Release historydanger

The latest release was over 6 years ago, with no releases in the last 12 months; this is strong evidence of abandonment risk despite an earlier history of 11 releases.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's long release gap and indicating no observed ongoing maintenance.

Licensecaution

Neither the package nor the linked repository declares or contains a recognized license, leaving developers without clear permission to use or redistribute the code.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene concern rather than evidence that the release is unsafe.

Security policycaution

The linked repository has no security policy, so there is no documented channel or process for reporting vulnerabilities; this is a transparency gap for a web integration package.