Package Health/temant/encryption-manager

temant/encryption-manager

Usable with caveats, especially for a security-sensitive encryption library. The repository is active and includes tests, but the package has had no registry release in over a year, all recent commits come from one maintainer, and no security policy is published.

Latest 1.0.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Release history

The package has only four releases and none in the last 12 months; its latest registry release was over a year ago, which raises maintenance and freshness concerns despite the relatively short historical release intervals.

Repo bus factor

All six recent commits came from one contributor, leaving maintenance highly dependent on a single person and creating continuity risk.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected; for an encryption library, this is a meaningful transparency gap.

Security policy

No repository security policy was found. This matters more for an encryption library because users lack documented guidance for reporting vulnerabilities and receiving security fixes.

Token permissions

The CI workflow does not declare top-level token permissions. Although no write permissions were observed, explicit least-privilege settings would provide stronger workflow transparency.