# What is wrong with the NPM repository?

**URL:** <https://community.sonatype.com/t/what-is-wrong-with-the-npm-repository/15574>\
**Category:** Sonatype Nexus Repository\
**Created:** [September 18, 2025, 6:21pm UTC](https://community.sonatype.com/t/what-is-wrong-with-the-npm-repository/15574 "2025-09-18T18:21:07Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![roland.asmann](https://avatars.discourse-cdn.com/v4/letter/r/22d042/32.png) [@roland.asmann](https://community.sonatype.com/u/roland.asmann)\
**Post date:** [September 18, 2025, 6:21pm UTC](https://community.sonatype.com/t/what-is-wrong-with-the-npm-repository/15574/1 "2025-09-18T18:21:07Z")

</div>

I’ve been setting up and testing a bit with NPM repositories and have now had my cleanup policies run. By my rules, the repo should currently be empty, but for some reason I see this in the repo:

 ![Screenshot 2025-09-17 at 13-30-55 Browse - Nexus Repository Manager](https://canada1.discourse-cdn.com/flex047/uploads/communitysonatype/original/2X/7/736e60e79483bfc0e7328b76a2870ef9b0c15011.png)  
When selecting these entries, I get the option to ‘Delete asset’, although I believe these should all be folders when filled…

What are these entries and why are they here? And more importantly, do they count toward my component/asset limit, even though in actuality nothing is there?

---

_[View the full topic](https://community.sonatype.com/t/what-is-wrong-with-the-npm-repository/15574)._