nuewire/filesystem
Usable with caveats: the package is licensed, documented, tested in its repository, and actively releasing, but it is only 51 days old and all recent commits come from one contributor. Its organization backing helps, though the lack of a security policy and very limited project history reduce confidence.
68%
Total Score
88
100
89
90
Health Score Breakdown
The package is very young at 51 days old, with seven releases clustered into roughly one day. This shows active initial iteration but provides little evidence of long-term maintenance.
All 10 recent commits came from one contributor, creating a real continuity risk. Organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a transparency gap rather than evidence of a defect.
No security policy is present in the repository, leaving vulnerability reporting and response expectations unclear for a package that handles filesystem settings.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Nuewire |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^1.1|^2.0|^3.0 | — | — |
illuminate/auth Version ^11.0|^12.0|^13.0 | — | — |
nuewire/support Version ^1.0 | — | — |
livewire/livewire Version ^3.6|^4.0.3 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 month 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.