Cookie consent, policy versions and privacy requests (export and erasure) for Filagora.
64%
Total Score
caution
A first v0.1.0 release has one contributor and broad, unpinned workflow access despite solid project documentation.
This is the first release, published 0 days ago, so there is no track record yet for sustained maintenance or release cadence.
One contributor accounts for all commits in the last three months, leaving maintenance dependent on a single active individual. Organization backing partly reduces handoff risk but does not show a second active maintainer.
Only one commit was recorded in the last three months, so actual ongoing maintenance activity is not yet demonstrated, even though the release is new.
Composer build tooling is present, but no security scanning tool was detected. For a brand-new package this is a modest transparency and maintenance gap, not a severe risk.
Version v0.1.0 is not a stable major release, and the README explicitly says the API may change between 0.x minor versions. That increases adoption and compatibility risk, though it is not evidence of abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^5.0 | — | — |
filagora/filagora-core Version ^0.2.1 | — | — |
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.