Get Help
Find answers in our documentation, troubleshoot common issues, or reach out to our support team for personalized assistance.
Get Help Your Way
Browse by Topic
Getting Started
Learn the basics of Li'nage Cloud—from creating your account to understanding your first dependency graph.
CLI & Ingestion
Connect your repositories, configure the linage CLI, and automate supply chain tracking in your CI/CD pipeline.
Visual Intelligence
Master the 3D Dependency Graph, Impact Analysis, and Risk Heatmaps to understand your ecosystem.
Security & Supply Chain
Understand supply chain risks, configure audit logging, and implement enterprise governance policies.
Billing & Account
Manage your organization subscriptions, understand usage limits, and configure team seat licensing.
API & Developers
Explore our API documentation and SDKs for custom integrations, automation, and reporting.
Common Issues & Solutions
Graph not loading or showing errors
The 3D dependency graph fails to render, shows a blank space, or displays WebGL errors.
- 1Ensure you're using a modern browser (Chrome, Firefox, Edge) with hardware acceleration enabled
- 2Check if your GPU drivers are up to date
- 3Try reducing visible nodes using the filter controls
- 4Clear browser cache and reload the page
CLI not detecting dependencies
The linage CLI runs successfully but reports fewer dependencies than expected or misses certain packages.
- 1Verify manifest files (package.json, requirements.txt, etc.) are present in the project root
- 2Ensure lock files exist—we need exact versions, not just version ranges
- 3Run `linage debug` to see exactly what files the CLI detects
- 4Check for non-standard project structures that may need explicit configuration
API authentication failures
API requests return 401 Unauthorized errors despite using a valid-looking API key.
- 1Verify your API key has the required scopes for your operation
- 2Confirm you're using a key from the correct organization
- 3Allow 30 seconds for newly created keys to propagate
- 4Check if the key was regenerated (old keys are immediately invalidated)
Need direct assistance?
Our support team consists of software engineers with deep expertise in dependency management and supply chain security.
Enterprise Priority Support
Direct access to senior engineers via dedicated Slack channel or priority ticket queue.
General Support
For bug reports, billing inquiries, and feature requests. Available 24/5.
Contact SupportQuick Answers
View All FAQs →How does Li'nage Cloud handle sensitive data?
Li'nage only processes metadata related to your software supply chain—dependencies, API endpoints, and architectural patterns. We never store or access your actual source code.
Can I use Li'nage with private GitHub Enterprise or GitLab instances?
Yes. Li'nage Cloud supports self-hosted CI/CD runners and private VCS instances. The CLI runs entirely within your infrastructure and only transmits processed metadata.
What is 'Blast Radius' analysis and why is it important?
Blast Radius calculates all downstream dependencies of any component. When a vulnerability is disclosed, Li'nage instantly identifies every affected application and service.
How quickly are new package versions detected?
With CI/CD integration, new versions are detected within seconds of a successful build. With manual CLI runs, detection happens immediately when you run the command.
System Status
All systems operational.