t4web/filesystem

Release historydanger

The package has only one release, published in March 2016, with no releases in the subsequent 12 months of the assessment window. This is strong evidence of an effectively inactive release line.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the package's extended lack of releases. No provided activity signal compensates for this maintenance gap.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a minor transparency and hygiene gap alongside the much more significant age and inactivity concerns.

Security policycaution

The repository has no security policy. For a small, old package this is a modest disclosure gap, though it is less significant than the lack of maintenance activity.