spryker/file-system

Release historycaution

The package has existed since 2017 and released once in the last 12 months, but its median release interval is about 11 months. Recent repository activity and the current release partly compensate for the slow cadence.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and hygiene gap, not evidence of unsafe behavior by itself.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package that handles filesystem and storage operations.

Workflow auditcaution

The only workflow was fully analyzed with no audit findings, no untrusted checkouts, and no script injection; however, two of four action references are unpinned, which is a minor reproducibility gap.