Say that the repository is archived, and send the security reports to ChromaDB.Client

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-The provider moved to [CommunityToolkit.VectorData.Chroma](https://www.nuget.org/packages/CommunityToolkit.VectorData.Chroma) and is developed in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI): open issues and pull requests there. This repository will be archived.
+The provider moved to [CommunityToolkit.VectorData.Chroma](https://www.nuget.org/packages/CommunityToolkit.VectorData.Chroma) and is developed in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI): open issues and pull requests there. This repository is archived.
 
 ## Build and test
 

README.md

@@ -5,17 +5,15 @@
 [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/ChromaDotNet/ChromaDB.VectorData/badge)](https://scorecard.dev/viewer/?uri=github.com/ChromaDotNet/ChromaDB.VectorData)
 [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/15279/badge)](https://www.bestpractices.dev/projects/15279)
 
-> **Moved to [CommunityToolkit.VectorData.Chroma](https://www.nuget.org/packages/CommunityToolkit.VectorData.Chroma),** in the [AI Community Toolkit](https://github.com/CommunityToolkit/AI), where the provider is developed now. The `ChromaDotNet.VectorData` package is deprecated, and this repository will be archived.
+> **Moved to [CommunityToolkit.VectorData.Chroma](https://www.nuget.org/packages/CommunityToolkit.VectorData.Chroma)**, in the [AI Community Toolkit](https://github.com/CommunityToolkit/AI). This package is deprecated and this repository is archived.
 
 ## Moving
 
-The API is the same: change the package reference, from `ChromaDotNet.VectorData` to `CommunityToolkit.VectorData.Chroma`, and the namespace, from `ChromaDB.VectorData` to `CommunityToolkit.VectorData.Chroma`. The [package README](src/ChromaDB.VectorData/README.md) shows the commands.
+The API is the same. Change the package reference and the namespace to `CommunityToolkit.VectorData.Chroma`. The [package README](src/ChromaDB.VectorData/README.md) shows the commands.
 
 ## History
 
-This repository published the `ChromaDotNet.VectorData` package, a [Chroma](https://www.trychroma.com/) provider for [Microsoft.Extensions.VectorData](https://learn.microsoft.com/dotnet/ai/vector-stores/overview) built on [ChromaDB.Client](https://github.com/ChromaDotNet/ChromaDB.Client), from 0.1.0 to 0.4.4. From 0.4.0 it had the same code as `CommunityToolkit.VectorData.Chroma`, which the AI Community Toolkit accepted in [CommunityToolkit/AI#58](https://github.com/CommunityToolkit/AI/pull/58).
-
-The provider started as a copy, under the MIT license, of the Qdrant provider in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI). It was then adapted to Chroma.
+A [Chroma](https://www.trychroma.com/) provider for [Microsoft.Extensions.VectorData](https://learn.microsoft.com/dotnet/ai/vector-stores/overview), built on [ChromaDotNet.Client](https://github.com/ChromaDotNet/ChromaDB.Client), published from 0.1.0 to 0.4.4. It started as a copy of the Qdrant provider in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI), under the MIT license. The AI Community Toolkit accepted it in [CommunityToolkit/AI#58](https://github.com/CommunityToolkit/AI/pull/58).
 
 > This is a community project. It is not affiliated with or endorsed by Chroma.
 

SECURITY.md

@@ -10,7 +10,7 @@ The form below takes reports about this package. It also takes reports about `Co
 
 Please do not report a vulnerability in a public issue, discussion or pull request.
 
-Report it privately on GitHub instead: [Report a vulnerability](https://github.com/ChromaDotNet/ChromaDB.VectorData/security/advisories/new), in the **Security** tab of this repository. Only the maintainers see the report.
+Report it privately on GitHub instead, in the [ChromaDB.Client](https://github.com/ChromaDotNet/ChromaDB.Client) repository, which has the same maintainers: [Report a vulnerability](https://github.com/ChromaDotNet/ChromaDB.Client/security/advisories/new). This repository is archived and does not take reports. Only the maintainers see the report.
 
 Include the version of the package, the version of Chroma or Chroma Cloud, and the steps to reproduce the problem.
 

src/ChromaDB.VectorData/README.md

@@ -25,9 +25,7 @@ The registrations, like `AddChromaVectorStore`, keep their names and their names
 
 ## History
 
-ChromaDotNet.VectorData was a [Chroma](https://www.trychroma.com/) provider for [Microsoft.Extensions.VectorData](https://learn.microsoft.com/dotnet/ai/vector-stores/overview), built on [ChromaDotNet.Client](https://github.com/ChromaDotNet/ChromaDB.Client). From 0.4.0 it had the same code as `CommunityToolkit.VectorData.Chroma`, which the AI Community Toolkit accepted in [CommunityToolkit/AI#58](https://github.com/CommunityToolkit/AI/pull/58). The provider is developed there now.
-
-It started as a copy, under the MIT license, of the Qdrant provider in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI), and was then adapted to Chroma. The releases and their notes are on [GitHub](https://github.com/ChromaDotNet/ChromaDB.VectorData/releases).
+A [Chroma](https://www.trychroma.com/) provider for [Microsoft.Extensions.VectorData](https://learn.microsoft.com/dotnet/ai/vector-stores/overview), built on [ChromaDotNet.Client](https://github.com/ChromaDotNet/ChromaDB.Client), published from 0.1.0 to 0.4.4. It started as a copy of the Qdrant provider in [CommunityToolkit/AI](https://github.com/CommunityToolkit/AI), under the MIT license. The AI Community Toolkit accepted it in [CommunityToolkit/AI#58](https://github.com/CommunityToolkit/AI/pull/58). The releases and their notes are on [GitHub](https://github.com/ChromaDotNet/ChromaDB.VectorData/releases).
 
 > This is a community project. It is not affiliated with or endorsed by Chroma.