bpa/notifications-stride
The single-user project is extremely small, with no tests, changelog, README, or security policy, and no repository security scanning. Its MIT declaration and simple Composer dependency set are positives, but they do not offset the long abandonment risk.
36%
Total Score
25
69
75
Health Score Breakdown
The package has had only two releases, with the latest published over eight years ago and none in the last 12 months, indicating sustained abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and leaving little evidence of ongoing maintenance.
One registry maintainer can be adequate for a small package, but here the narrow publishing base provides little resilience alongside the lack of recent project activity.
The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the absent README reduces consumer transparency for this library.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide no supporting evidence of broad adoption or community oversight.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Benjamin Paap |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 bpa/notifications Version ^1.0 | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.