Define uninitialized elements
76%
Total Score
healthy
Healthy: active maintenance and documented releases outweigh workflow hygiene gaps and the package-to-repository naming mismatch.
No build attestation or trusted-publisher provenance is present, so consumers have less verifiable evidence about how this release was produced.
The repository name does not match the package name and its README does not mention this package, so the package-to-source relationship is less transparent even though it may be a monorepo subpackage.
The repository uses established build tools including TypeScript, Rollup, Babel, and Vitest. It reports no security scanning tools, which is a modest transparency gap.
The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear.
All 19 analyzed action references are unpinned, and the release workflow installs packages outside a lockfile; both weaken reproducibility. However, there are no untrusted checkouts or script-injection findings, and the audit covered all three workflows.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
scheduler Version 0.25.0-rc-603e6108-20241029 | — | — |
object-assign Version ^4.1.1 | — | — |
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.