newageerp/sf-filesmanager

Release historydanger

The package has four releases, but all activity occurred on its first day and there have been no releases for about four years. That is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving maintenance capacity un demonstrated.

Package file treecaution

The artifact and repository each contain only four files, including two PHP classes and composer.json. This may be intentionally minimal, but it provides little visible project depth or maintenance evidence.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counters provide no additional confidence in long-term project backing.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security-scanning tools are present. This is a modest hygiene gap rather than a standalone dependency blocker.