gizburdt/talk
Documentation and basic project structure are in place. Its age leaves maintenance capacity unproven, while workflow hardening is incomplete.
68%
Total Score
100
79
75
Health Score Breakdown
The package is only 0 days old, with three releases published within hours, so there is not yet enough history to demonstrate sustained maintenance. The rapid initial releases show active setup but do not offset the lack of a longer track record.
Composer build tooling is present, but no security-scanning tool is reported. For this new package, the missing scanning layer is a modest transparency and maintenance gap.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, though it is not severe enough to make the release unfit on its own.
Version 0.3.0 is not a prerelease, which is positive, but the pre-1.0 version still indicates that compatibility and API maturity are not established.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 5 action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Gijs Jorissen |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version ^12.0||^13.0 | — | — |
illuminate/support Version ^12.0||^13.0 | — | — |
illuminate/notifications Version ^12.0||^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 21 hours ago
- Created
- 1 day 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.