laravel-notification-channels/microsoft-teams
Clear licensing, tests, release notes, and an organization-backed repository support adoption. Workflow references are all unpinned and no security policy is published, leaving avoidable maintenance and build-hygiene gaps.
70%
Total Score
75
100
94
50
Health Score Breakdown
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The regular release history partly offsets this, but the lack of recent development activity is a meaningful maintenance concern.
Composer is used for builds, but no security-scanning tools are detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no published security policy, leaving vulnerability reporting and response expectations undocumented.
Both workflows were analyzed successfully with no high-confidence audit findings or untrusted checkouts, but all 5 action references are unpinned and one workflow grants top-level write access. With no untrusted trigger or sink, this is workflow hygiene caution rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tobias Madner |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^12.0 || ^13.0 | — | — |
illuminate/notifications Version ^12.0 || ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 months ago
- Created
- 6 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.