Clear documentation, licensing, and a small runtime dependency set make integration straightforward. The source remains available and organization-backed, but the project lacks a published security policy and has limited recent development activity.
58%
Total Score
75
100
88
75
The package has had no registry releases in the last six years, with its latest release on January 11, 2020. This is a meaningful freshness and maintenance concern, though the linked repository was pushed more recently.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the absence of registry releases for about six years, this indicates limited current development capacity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no published security policy. That reduces transparency for reporting and handling vulnerabilities, although it is not evidence of a vulnerability by itself.
Both workflows were analyzed successfully with no dangerous triggers, sinks, or audit findings. However, both action references are unpinned, leaving a modest supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
brightnucleus/config Version >=0.2 | — | — |
brightnucleus/invoker Version >=0.1 | — | — |
brightnucleus/contracts Version >=0.1 | — | — |
brightnucleus/exceptions Version >=0.2 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.