A complete source tree, tests, MIT licensing, and a security policy improve transparency. The package has only one release and no commits in the last three months; zero adoption signals and unpinned CI actions add maintenance and build-integrity concerns.
60%
Total Score
50
83
83
The package and repository are associated with a user account rather than an organization. This does not establish project backing beyond the individual publisher, so it offers limited maintenance assurance.
This is a young package, about three and a half months old, with only one release and no established release cadence. That limits evidence of sustained maintenance, though the short history does not by itself show abandonment.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only about three and a half months old, this leaves ongoing maintenance unproven and raises abandonment risk.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the complete absence of adoption signals provides no external indication of maturity.
Composer build tooling is present, but no security scanning tool was detected. This is a modest repository-hygiene gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
switon/di Version ^1.0 | — | — |
switon/core Version ^1.0 | — | — |
switon/pool Version ^1.0 | — | — |
switon/event Version ^1.0 | — | — |
switon/command Version ^1.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.