Large number of package.json.tmpxxxxxxxxxx files under /verdaccio/storage/data/npm when installed via Helm - how should they be cleaned up correctly?

[killinitzero]

Hi Verdaccio team,

We are using Verdaccio deployed via Helm on Kubernetes, and we have noticed a large number of temporary files like the following under:

/verdaccio/storage/data/npm

Examples:

• package.json.tmp1234567890
• package.json.tmp0987654321

Over time, these .tmp files have accumulated in significant numbers.

We would like to understand:

1. What is the purpose of these package.json.tmpxxxxxxxxxx files?
2. Under what conditions are they left behind?
3. Are they safe to delete manually when Verdaccio is stopped?
4. Is there an officially recommended cleanup procedure for these files?
5. Is this expected behavior, or could it indicate an incomplete write / interrupted process / storage issue?

Our main concern is how to clean them up correctly without risking metadata inconsistency or package corruption.

Environment:

• Verdaccio installed via Helm
• Storage path: /verdaccio/storage/data/npm
• Running on Kubernetes

If needed, we can provide:

• Verdaccio version
• Helm chart version
• storage backend details
• logs around package publish / sync operations

Thanks.

[juanpicado]

It happens time in time whenever the storage is not able to remove temp files. Why it happens die while a tarball is streamed fails or is interrupted the temp files get there. It is safe to remove since the temp is renames once streams ends. I can investigate but I might need to know more info, versions config, plugins etc

[mbtools]

What's "many"? For every package? If yes, it seems a systemic issue which we should look into. Please post Verdaccio version and config.