glaivepro/sf

Release historycaution

Only two releases exist, both from the same day, and there has been no release for over two years. That makes ongoing compatibility and maintenance less certain.

Repo commit activitycaution

There were no commits and no active maintainers during the last three months. Combined with the old latest registry release, this indicates limited current maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, though it does not by itself show abandonment.

Version stabilitycaution

Version 0.2.0 is not a stable major release, which adds some API-change risk for consumers. The package is not marked as a prerelease, so this is a moderate concern rather than a severe one.