The project has a maintained source repository, tests, a clear README, and a release note for this version. Recent repository activity is quiet, with no commits in three months, while the workflow uses one unpinned action and the repository has no security policy.
72%
Total Score
67
100
88
67
The registry namespace and repository owner match, showing that the linked repository belongs to the package publisher. The owner is an individual account rather than an organization, so long-term bus-factor support is limited.
The repository recorded zero commits and zero active maintainers in the last three months. Although a recent release and push show some maintenance, the current quiet period raises a modest maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. For a package handling encrypted data, that is a meaningful transparency and maintenance gap.
The repository has no security policy. For an encryption-focused package, the lack of a documented vulnerability reporting process weakens security transparency.
The assessed release is marked stable and is not a prerelease, but the reported latest version is 4.1.5 while the assessed version is 5.0.0, creating a release metadata inconsistency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/assets Version ^3 | — | — |
paragonie/ciphersweet Version ^4.8 | — | — |
silverstripe/framework Version ^6 | — | — |
silverstripe/recipe-plugin Version ^2.1 | — | — |
silverstripe/vendor-plugin Version ^3 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.