Instructions to use vidore/colpali with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- ColPali
How to use vidore/colpali with ColPali:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- sentence-transformers
How to use vidore/colpali with sentence-transformers:
from sentence_transformers import MultiVectorEncoder model = MultiVectorEncoder("vidore/colpali") queries = ["Which planet is known as the Red Planet?"] documents = [ "Venus is often called Earth's twin because of its similar size and proximity.", "Mars, known for its reddish appearance, is often referred to as the Red Planet.", "Jupiter, the largest planet in our solar system, has a prominent red spot.", ] query_embeddings = model.encode_query(queries) document_embeddings = model.encode_document(documents) similarities = model.similarity(query_embeddings, document_embeddings) print(similarities) - Notebooks
- Google Colab
- Kaggle
Add LICENSE file
Browse filesThis pull request adds a LICENSE file to the repository based on the license declared in your repository metadata.
### Background
Your repository declares the `MIT` license in its HuggingFace metadata (`license:mit`), but does not currently include a LICENSE file in the repository. This creates legal ambiguity and makes it harder for users to understand the exact terms under which they can use your work.
### What This PR Does
This PR adds a standard `LICENSE` file containing the full text of the **MIT License**, with:
- Copyright holder: `vidore` (repository owner)
- Copyright year: `2025` (based on first commit)
### Why This Matters
Having an explicit LICENSE file in your repository:
- ✅ Provides clear legal terms for users
- ✅ Matches your declared license metadata
- ✅ Makes it easier for others to comply with your license
- ✅ Improves repository completeness and professionalism
### Please Review
**Important:** Please verify that:
1. The copyright holder is correct (I've used the repository owner: `vidore`)
2. The copyright year is appropriate (I've used the first commit year: `2025`)
3. The license matches your intent (based on your metadata: `MIT`)
If any of these need to be updated, please let me know and I'll gladly adjust the LICENSE file!
### References
- License metadata: `license:mit`
- SPDX specification: https://opensource.org/license/mit/
---
🤖 Generated with automated license compliance tooling
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
MIT License
|
| 2 |
+
|
| 3 |
+
Copyright (c) 2025 vidore
|
| 4 |
+
|
| 5 |
+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
|
| 6 |
+
associated documentation files (the "Software"), to deal in the Software without restriction, including
|
| 7 |
+
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
| 8 |
+
copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
|
| 9 |
+
following conditions:
|
| 10 |
+
|
| 11 |
+
The above copyright notice and this permission notice shall be included in all copies or substantial
|
| 12 |
+
portions of the Software.
|
| 13 |
+
|
| 14 |
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
|
| 15 |
+
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
|
| 16 |
+
EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
|
| 17 |
+
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
|
| 18 |
+
USE OR OTHER DEALINGS IN THE SOFTWARE.
|