# Why is the Numlock repo not marked deprecated

**URL:** https://community.keyboard.io/t/why-is-the-numlock-repo-not-marked-deprecated/1618
**Category:** Kaleidoscope Internals
**Created:** [June 12, 2018, 4:35am UTC](https://community.keyboard.io/t/why-is-the-numlock-repo-not-marked-deprecated/1618 "2018-06-12T04:35:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jamadagni](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/jamadagni/32/2030_2.png) [@jamadagni](https://community.keyboard.io/u/jamadagni)
#### Post date: [June 12, 2018, 4:35am UTC](https://community.keyboard.io/t/why-is-the-numlock-repo-not-marked-deprecated/1618/1 "2018-06-12T04:35:20Z")

</div>

I found that there are two plugins [NumPad](https://github.com/keyboardio/Kaleidoscope-NumPad) and [Numlock](https://github.com/keyboardio/Kaleidoscope-Numlock).

From the discussion [On the history and implementation of NumLock](https://community.keyboard.io/t/on-the-history-and-implementation-of-numlock/735):

it seems that NumPad is the updated version of Numlock. If there was a problem with the earlier logic, why not just fix in the same plugin? At least now the earlier repo must be marked deprecated or such, no?

---

<div class="post-metadata">

### Author: ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)
#### Post date: [June 12, 2018, 4:59am UTC](https://community.keyboard.io/t/why-is-the-numlock-repo-not-marked-deprecated/1618/2 "2018-06-12T04:59:25Z")

</div>

We were debating which is the right approach, hence the completely new plugin. As for why not deprecating NumLock yet - because I never got around to it, and simply forgot. I’m opening an issue to remind myself to do it.