There is no security policy or repository security scanning, and all six workflow actions are unpinned. The package is clearly tied to an organization-owned repository, but its two-release history and no commits in three months limit maintenance confidence.
64%
Total Score
75
100
88
50
The package is about seven months old with only two releases, and the latest was about four months ago. This is limited maintenance evidence, though the project is still relatively young.
There were no commits and no active maintainers in the last three months. For a package released only twice, that leaves limited evidence of ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence of a direct defect.
The repository has no security policy, so users have no documented reporting or response process for vulnerabilities.
The workflow audit completed fully with no detected injection or dangerous-workflow findings, and it scopes no top-level write permissions. However, all six action references are unpinned, leaving builds exposed to action changes over time.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^4.0 | ^5.0 | — | — |
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.