spryker/file-system-extension

Release historycaution

Only two releases exist over roughly five years, with a long interval between them, which limits maturity evidence; the release in the last year and recent repository activity partly compensate.

Repo toolingcaution

Composer build tooling is present, but no repository security-scanning tool was detected; this is a modest transparency and assurance gap.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting expectations unclear; organization backing provides some compensating maintenance context but not a replacement policy.

Workflow auditcaution

The sole workflow was fully analyzed with no dangerous audit findings, no untrusted checkout, and no script injection. Two of four action references are unpinned, so supply-chain reproducibility is only partial; the lack of a top-level permissions block is acceptable on its own.