The project has had no commits in three months and no releases in the past year. Its tiny user base, absent security policy, and unpinned workflow actions add maintenance and build-transparency concerns, though the repository is active rather than archived and the release is clearly licensed.
58%
Total Score
75
100
83
67
The package has existed since January 2016 with 11 releases, but it has had no release in the past 12 months. That suggests a mature but currently slow release cadence.
There were zero commits and zero active maintainers in the last three months. That is a concrete sign of currently limited maintenance capacity.
The repository has 1 star, 1 fork, and 3 watchers. This very small user base offers little external validation or maintenance resilience.
The repository uses Composer, but no security scanning tools are reported. The missing scanning coverage is a modest transparency and maintenance concern.
The repository has no security policy. For a small exporter this is not independently severe, but it leaves vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^3.0 | — | — |
ntlab/php-obj Version ^1.0 | — | — |
mysql-workbench-schema-exporter/mysql-workbench-schema-exporter Version ^4.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.