# Juliahub packages feature request: detect and mark deprecated or archived packages

**URL:** <https://discourse.julialang.org/t/juliahub-packages-feature-request-detect-and-mark-deprecated-or-archived-packages/97370>\
**Category:** General Usage\
**Tags:** deprecation, juliahub\
**Created:** [April 11, 2023, 11:29pm UTC](https://discourse.julialang.org/t/juliahub-packages-feature-request-detect-and-mark-deprecated-or-archived-packages/97370 "2023-04-11T23:29:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Post date:** [April 11, 2023, 11:29pm UTC](https://discourse.julialang.org/t/juliahub-packages-feature-request-detect-and-mark-deprecated-or-archived-packages/97370/1 "2023-04-11T23:29:22Z")

</div>

1. Perhaps there should be a feature to mark your package as deprecated on Juliahub?

2. Once a package’s source code repository get’s archived, I think it would make sense for this fact to be prominently displayed on Juliahub, including in the search results.

For example, searching for `JET` includes the `JETTest` result, whose Github repo is archived, but one only finds this out once on Github: [JuliaHub](https://juliahub.com/ui/Packages/JETTest/up2h3/0.1.4)

Related thread:

> [@Procedures for package renaming, deletion and deprecation](https://discourse.julialang.org/t/procedures-for-package-renaming-deletion-and-deprecation/48108/):
>
> I want to highlight a recent experience regarding this subject and offer some criticism and suggestions in the spirit of improving the Julia ecosystem. A few days ago I registered a new websocket (generic tech term) library, calling it Websocket. This was automerged into the General Registry after the 3 day wait for new packages. I was subsequently asked by a registry moderator to rename this package because of potential confusion with the pre-existing WebSockets package. Fair enough, but thi…

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [April 12, 2023, 12:11am UTC](https://discourse.julialang.org/t/juliahub-packages-feature-request-detect-and-mark-deprecated-or-archived-packages/97370/2 "2023-04-12T00:11:28Z")

</div>

I believe you wanted to open an issue at [GitHub - JuliaComputing/JuliaHub-Feedback: Public repo for filing JuliaHub issues](https://github.com/JuliaComputing/JuliaHub-Feedback)

---

<div class="post-metadata">

**Author:** ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Post date:** [April 12, 2023, 7:01am UTC](https://discourse.julialang.org/t/juliahub-packages-feature-request-detect-and-mark-deprecated-or-archived-packages/97370/3 "2023-04-12T07:01:52Z")

</div>

Turns out a ticket exists already, although closed (EDIT: reopened):

> <https://github.com/JuliaComputing/JuliaHub-Feedback/issues/43>
>
> Both the package overview and the package detail pages should probably indicate …archived packages somehow. We could maybe even penalize them in the package search.