campaigningbureau/facebook-repository
Security coverage is thin, with no automated scanning or security policy. The MIT license, focused repository, and usable README improve transparency but do not offset the stale maintenance picture.
42%
Total Score
75
75
50
Health Score Breakdown
The latest release was in September 2018, with no releases in the last 12 months and only two releases overall. This long period without publishing materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in March 2022, current maintenance activity is absent.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap for a package handling external API credentials.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a genuine transparency gap, though it is not by itself evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Stefan Schindler |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/cache Version 5.5.* | — | — |
illuminate/support Version 5.5.* | — | — |
sammyk/laravel-facebook-sdk Version ^3.5 | — | — |
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.