railken/amethyst-employee
The repository has tests, a clear MIT license, and organizational backing. Its CI still uses an unpinned container image, and there is no security policy or scanning, increasing maintenance and build-integrity concerns.
40%
Total Score
50
70
50
Health Score Breakdown
The latest release was about 6 years ago, with no releases in the last 12 months. Although the package had 15 releases and a fast earlier cadence, current maintenance appears stalled.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of abandonment by itself.
No security policy was found in the repository, leaving vulnerability reporting and response expectations undocumented.
All 6 analyzed action references are unpinned, and the audit found a high-confidence unpinned container image in test.yml. The workflows have no top-level permissions block, which is acceptable on its own, but the unpinned image weakens build reproducibility.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 amethyst/core Version 0.2.* | — | — |
amethyst/office Version 0.2.* | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.