lyfter/amp-fswatch

Release historycaution

Only two releases have appeared over about eight months, with roughly four months between releases. That is limited maintenance evidence for a relatively young package, though it is not abandonment by itself.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months. For a package with only two releases, this is a meaningful maintenance warning.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no SECURITY.md or other security policy, leaving vulnerability reporting expectations unclear.

Workflow auditcaution

The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, or audit findings, but all 9 action references are unpinned. That leaves CI exposed to unexpected action changes.