# How to Get Support for Graphify: Channels, Documentation, and Community Resources

> Need Graphify support? Discover official channels including GitHub Issues, Discord chat, and LinkedIn. Find quick answers and community help in our documented resources.

- Repository: [Graphify Labs/graphify](https://github.com/Graphify-Labs/graphify)
- Tags: getting-started
- Published: 2026-07-19

---

**Graphify provides official support through GitHub Issues for bug tracking, Discord for real-time community chat, LinkedIn for business inquiries, and SECURITY.md for confidential vulnerability disclosures, all linked in the repository's README.md.**

Getting timely assistance with Graphify requires knowing which channel matches your specific need. The Graphify-Labs/graphify repository maintains several communication pathways documented in [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) and supporting metadata files. Whether you encounter installation errors with the platform-specific commands or need to discuss architectural changes, the project offers structured avenues for both users and contributors.

## Primary Support Channels

### GitHub Issues for Technical Problems

The main venue for reporting bugs, requesting features, and asking technical questions is the GitHub Issues tracker at `https://github.com/Graphify-Labs/graphify/issues`. This link appears at the top of [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) and serves as the permanent record for all technical problems.

When submitting an issue, reference the three output files generated by Graphify ([`graph.html`](https://github.com/Graphify-Labs/graphify/blob/main/graph.html), [`GRAPH_REPORT.md`](https://github.com/Graphify-Labs/graphify/blob/main/GRAPH_REPORT.md), [`graph.json`](https://github.com/Graphify-Labs/graphify/blob/main/graph.json)) documented in the README's "Get started" section. Include specific commands used, such as `graphify --update`, and any relevant environment details.

```bash

# Open a new GitHub issue using the GitHub CLI

gh issue create --title "Unexpected node count after --update" \
                --body "I ran `graphify --update` on my project and the resulting graph lost several nodes..."

```

### Discord Community for Real-Time Chat

For immediate troubleshooting and community discussion, join the official Discord server via the badge link located in [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) lines 20-23. The invitation URL is `https://discord.gg/598Ad9zQZ`.

This channel connects you directly with maintainers and active users for quick questions about installation commands or integration with AI assistants documented in [`AGENTS.md`](https://github.com/Graphify-Labs/graphify/blob/main/AGENTS.md). The maintainers monitor Discord actively for urgent issues that require rapid iteration.

```bash

# Join the Discord server (macOS)

open https://discord.gg/598Ad9zQZ

```

### LinkedIn and Y Combinator Network

Business inquiries, partnership opportunities, and general announcements should route through LinkedIn at `https://www.linkedin.com/company/graphify-labs`, referenced in [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) lines 22-23.

For Y Combinator alumni, the repository displays a YC alumni badge that enables high-visibility outreach for YC-related queries. This channel is appropriate for strategic discussions rather than technical debugging.

## Specialized Support Pathways

### Security Vulnerability Reporting

Do not use public GitHub Issues for security problems. Instead, follow the private disclosure process outlined in [`SECURITY.md`](https://github.com/Graphify-Labs/graphify/blob/main/SECURITY.md). This file specifies how to submit vulnerability reports regarding sensitive components like the `graphify serve` command without public exposure.

```bash

# Submit a security report via email

cat <<EOF | mail -s "Security disclosure for Graphify" security@graphify.com
Hi Graphify team,

I discovered a potential vulnerability in the `graphify serve` command that…
EOF

```

### Code Contributions via Pull Requests

To directly improve the project, submit Pull Requests to `https://github.com/Graphify-Labs/graphify/pulls`. This pathway allows you to discuss implementation details with maintainers while referencing internal design documentation. Review [`ARCHITECTURE.md`](https://github.com/Graphify-Labs/graphify/blob/main/ARCHITECTURE.md) before submitting changes to core dependency graph algorithms.

## Documentation Files for Troubleshooting

Before opening a support request, consult these authoritative files in the repository root:

- **[`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md)** – Contains primary support links (Discord, LinkedIn, GitHub Issues) in lines 20-23, plus the "Get started" section covering installation and output files.
- **[`AGENTS.md`](https://github.com/Graphify-Labs/graphify/blob/main/AGENTS.md)** – Documents platform-specific install commands and hook mechanisms for AI assistant integration.
- **[`CHANGELOG.md`](https://github.com/Graphify-Labs/graphify/blob/main/CHANGELOG.md)** – Lists recent fixes and features to verify whether your issue is already resolved in the current version.
- **[`ARCHITECTURE.md`](https://github.com/Graphify-Labs/graphify/blob/main/ARCHITECTURE.md)** – Provides internal design overviews essential for discussing structural changes or deep technical concerns.
- **[`SECURITY.md`](https://github.com/Graphify-Labs/graphify/blob/main/SECURITY.md)** – Outlines confidential disclosure procedures and contact methods for vulnerability reports.

## Summary

- **GitHub Issues** serves as the primary channel for bug reports and feature requests regarding the `graphify` CLI and output files.
- **Discord** (linked in [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) lines 20-23) offers real-time chat support for installation and usage questions.
- **LinkedIn** handles business inquiries and partnerships, while the **Y Combinator alumni network** provides strategic outreach for YC-related matters.
- **SECURITY.md** governs private vulnerability disclosures for sensitive components like `graphify serve`.
- **Pull Requests** allow direct code contributions with maintainer review, supported by [`ARCHITECTURE.md`](https://github.com/Graphify-Labs/graphify/blob/main/ARCHITECTURE.md) and [`AGENTS.md`](https://github.com/Graphify-Labs/graphify/blob/main/AGENTS.md).

## Frequently Asked Questions

### How do I report a bug in Graphify?

Open a new issue at `https://github.com/Graphify-Labs/graphify/issues` with specific details about the command executed (such as `graphify --update`), your environment, and the three output files ([`graph.html`](https://github.com/Graphify-Labs/graphify/blob/main/graph.html), [`GRAPH_REPORT.md`](https://github.com/Graphify-Labs/graphify/blob/main/GRAPH_REPORT.md), [`graph.json`](https://github.com/Graphify-Labs/graphify/blob/main/graph.json)). The maintainers triage issues based on the README's documented behavior.

### Where can I get real-time help with Graphify installation?

Join the Discord server using the invite link in [`README.md`](https://github.com/Graphify-Labs/graphify/blob/main/README.md) lines 20-23 (`https://discord.gg/598Ad9zQZ`). This community channel is monitored by maintainers for quick troubleshooting of platform-specific install commands documented in [`AGENTS.md`](https://github.com/Graphify-Labs/graphify/blob/main/AGENTS.md).

### How do I report a security issue in Graphify?

Follow the process in [`SECURITY.md`](https://github.com/Graphify-Labs/graphify/blob/main/SECURITY.md) instead of opening a public issue. Send vulnerability details regarding commands like `graphify serve` to the security contact specified in that file to ensure private handling until a patch is released.

### How can I contribute fixes to Graphify?

Submit a Pull Request to `https://github.com/Graphify-Labs/graphify/pulls`. Reference [`ARCHITECTURE.md`](https://github.com/Graphify-Labs/graphify/blob/main/ARCHITECTURE.md) when proposing structural changes, and ensure your PR description explains implementation details clearly. This allows maintainers to review code changes against the project's internal design patterns.