Core Storybook Manager API & Context
88%
Total Score
100
100
94
80
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable despite the otherwise strong project evidence.
Three workflows use pull_request_target, which warrants review because that trigger can expose elevated privileges, but no untrusted checkout or script-injection patterns were detected across the 19 analyzed workflows.
The linked repository name does not match the package name and its README does not mention @storybook/manager-api, so the package-to-repository relationship is less transparent; the monorepo structure partly explains the name mismatch but not the absent README mention.
Most workflows use read-only or job-level permissions, but 4 workflows lack top-level permissions and 4 declare top-level write access, creating a modest workflow-hardening gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.