# All Repository Packages Containing Substring
**URL:** https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480
**Category:** New to Julia
**Created:** [September 25, 2018, 5:39pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480 "2018-09-25T17:39:31Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@iwelch](https://discourse.julialang.org/u/iwelch)
#### Post date: [September 25, 2018, 5:39pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/1 "2018-09-25T17:39:31Z")
If I want to find all packages on the Julia repository that contain the string “csv” (either in the title or the short description). I read the Pkg information again, but could not find a native Julia way. Fortunately, there is an easy alternative. For the most part, I have been relying on google and then on [https://pkg.julialang.org](https://pkg.julialang.org). This is fine if this is the recommended way to do this. Is it?
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [September 25, 2018, 5:46pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/2 "2018-09-25T17:46:38Z")
For registered packages, you can try searching [GitHub - JuliaLang/METADATA.jl: Metadata for registered Julia packages up to Julia v0.6. No longer maintained. Please see https://github.com/JuliaRegistries/General instead.](http://github.com/julialang/METADATA.jl) directly.
---
### Author:  [@iwelch](https://discourse.julialang.org/u/iwelch)
#### Post date: [September 25, 2018, 6:10pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/3 "2018-09-25T18:10:13Z")
> [@Sukera](#):
>
> For registered packages, you can try searching [github.com/julialang/METADATA.jl](http://github.com/julialang/METADATA.jl) directly.
From the link: **Sorry, we had to truncate this directory to 1,000 files. 1,280 entries were omitted from the list.**
and it does not have the short description.
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [September 25, 2018, 6:47pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/4 "2018-09-25T18:47:36Z")
In the upper left there should be a search field - that one can search just that repository.
Yeah, I think the short description is just the one set in each github repo separately - having a better way to search those would indeed be awesome.
---
### Author:  [@iwelch](https://discourse.julialang.org/u/iwelch)
#### Post date: [September 25, 2018, 8:58pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/5 "2018-09-25T20:58:08Z")
well, maybe “my” method looking through n [https://pkg.julialang.org](https://pkg.julialang.org/) works best. just hoping that it covers all packages…
---
### Author:  [@dpsanders](https://discourse.julialang.org/u/dpsanders)
#### Post date: [September 26, 2018, 11:13pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/6 "2018-09-26T23:13:19Z")
I believe [Pkg.julialang.org](http://Pkg.julialang.org) is no longer updated (?)
Try [juliaobserver.com](http://juliaobserver.com).
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [September 28, 2018, 2:47pm UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/7 "2018-09-28T14:47:02Z")
6 posts were split to a new topic: [Getting packages into Julia Observer](https://discourse.julialang.org/t/getting-packages-into-julia-observer/15616)
---
### Author:  [@Nosferican](https://discourse.julialang.org/u/Nosferican)
#### Post date: [September 27, 2018, 6:24am UTC](https://discourse.julialang.org/t/all-repository-packages-containing-substring/15480/8 "2018-09-27T06:24:12Z")
I have a few scripts in R I used to do similar things…
The approach I recommend is to
1. Parse the registry to find the package and repository (most are in Github)
- You get the name of the package here
2. Use the Github API to get the description and optionally parse the README
- If given a few months, packages can start using the `keywords` in the Project.toml and you can get these directly from the registry
3. Profit