@viby/sdk@0.3.17
Framework-agnostic SDK for building persistent, skill-guided vibe coding products.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged token flow is conditional on remote skill resolution during generation and is documented as authentication to the skills.sh API. GitHub credentials go to GitHub for repository lookups, and the package has no install-time hook.
Decision evidence
public snapshot- The README describes remote skills.sh resolution through its authenticated API when Vercel OIDC is available, with public GitHub as a fallback.
- The Vercel OIDC token is read only in the remote skill resolver and sent as a bearer token to skills.sh for that lookup.
- The resolver is called while processing a generation whose skills have not already been resolved.
- GitHub tokens, when configured, are sent to api.github.com for GitHub repository lookups.
- Remote skill resolution forwards VERCEL_OIDC_TOKEN to skills.sh; this is a cross-service credential flow, but the package documents it as authentication for that feature.
- The manifest has prepack and prepublishOnly scripts, but no install-time lifecycle hook.
Source & flagged code
5 flaggedPackage source references weak cryptographic algorithms.
dist/integration-vercel.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @viby/sdk@0.3.17.
See all versions of @viby/sdk for other recorded verdicts.
- Review the evidence and your use of @viby/sdk@0.3.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.