eflames/file-vault

Project backingcaution

The repository is owned by an individual account rather than an organization, so the single registry maintainer provides limited visible backing for ongoing maintenance.

Release historycaution

This package has only one release, published over three years ago, with no releases in the last 12 months. The linked repository is still available, but the registry release history indicates a stale distribution channel.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Although the repository was pushed in May 2025, the current activity profile raises maintenance and abandonment concerns.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. This reduces transparency for reporting vulnerabilities in a package that handles file encryption, though it is not by itself evidence of abandonment.