filament/notifications
A security policy is absent, while the small runtime dependency set keeps integration straightforward. Organization backing and the MIT license reduce the effect of the narrow recent contributor base.
80%
Total Score
83
100
93
75
Health Score Breakdown
One contributor made 100% of the 12 commits in the last 3 months. This is a maintenance concentration concern, partly offset by the repository being owned by an organization.
Composer is used as the build tool, but no security-scanning tooling was detected. The missing scanning tooling is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented, which modestly lowers transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 filament/actions Version self.version | — | — |
filament/support Version self.version | — | — |
Weekly Downloads
Info
- Last Published
- 19 hours ago
- Created
- 4 years 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.