docs: two broken file links (CONTRIBUTING license link, crewai-tools logo)

Open Beginner friendly
#7,599 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Start with .github/CONTRIBUTING.md line 176 and lib/crewai-tools/README.md line 3. Check the repository-root LICENSE and docs/images/crewai_logo.png paths, then update both Markdown links to the relative paths described in the issue. Done means the rendered license link resolves and the README logo displays without a broken-image marker.

Written by the indexing model from the issue text.

Description

AI-generated contribution: authored with AI assistance (per the Contributing guide). Please apply the llm-generated label — I don't have permission to add labels.

Description

Two file links 404 on GitHub:

  • .github/CONTRIBUTING.md line 176 links (LICENSE), which resolves to .github/LICENSE — that file doesn't exist; the MIT License lives at the repo root.
  • lib/crewai-tools/README.md line 3 embeds ./assets/crewai_logo.png, but lib/crewai-tools/assets/ doesn't exist. The logo lives at docs/images/crewai_logo.png.

Steps to Reproduce

  1. Open the rendered CONTRIBUTING.md and click the "MIT License" link → 404.
  2. Open the rendered crewai-tools README → the logo renders as a broken image.

Expected behavior

Both links resolve to the actual files (../LICENSE and ../../docs/images/crewai_logo.png respectively).

Screenshots/Code snippets

# .github/CONTRIBUTING.md, line 176
By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).

# lib/crewai-tools/README.md, line 3
![Logo of crewAI, two people rowing on a boat](./assets/crewai_logo.png)

Operating System

N/A (documentation only)

Python Version

N/A (documentation only)

Dominant language
Python
Stars
58.8k
Forks
8.5k
Avg merge
1d 13h
Merged PRs (30d)
103

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from crewAIInc/crewAI

All issues in crewAIInc/crewAI

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.