#Banned Dependency Detected! `leech`

78 messages · Page 1 of 1 (latest)

fervent elbow
#

Hi folks, I am trying to deploy my nodejs application on railway but it fails every time with the following message:

====================================
Banned Dependency Detected!
====================================

leech

Please remove this dependency from your project to use it on Railway

I have checked my package.json file and cannot find any direct reference to the leech. I suspect that the package may be a transitive dependency of one of the packages listed in my package.json file.

Here is a copy of my package.json file for your reference:

{ "name": "hoh-backend", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "prod": "pm2 start src/index.js", "build": "find ./src/ -name '*.js' -type f -delete && tsc", "dev": "ts-node-dev --respawn --pretty --transpile-only src/index.ts", "test": "echo \"Error: no test specified\" && exit 1", "lint": "eslint src --ext .ts" }, "keywords": [], "author": "", "license": "ISC", "dependencies": { "@pinata/sdk": "^1.1.26", "@types/node-fetch": "^2.6.2", "@types/swagger-ui-express": "^4.1.3", "canvas": "^2.9.3", "class-transformer": "^0.5.1", "class-validator": "^0.13.2", "cors": "^2.8.5", "dotenv": "^16.0.1", "ethers": "^5.6.9", "express": "^4.18.1", "helmet": "^5.1.0", "image-data-uri": "^2.0.1", "merge-images": "^2.0.0", "mongoose": "^6.4.2", "node-cron": "^3.0.1", "random-number-csprng": "^1.0.2", "reflect-metadata": "^0.1.13", "swagger-ui-express": "^4.6.0" }, "devDependencies": { "@types/cors": "^2.8.12", "@types/dotenv": "^8.2.0", "@types/express": "^4.17.13", "@types/helmet": "^4.0.0", "@types/merge-images": "^1.2.1", "@types/node": "^18.0.0", "@types/node-cron": "^3.0.2", "pm2": "^5.2.0", "ts-node-dev": "^2.0.0", "typescript": "^4.7.4" } }

Kindly guide me which of my packages could have this leech dependency problem.

tawny whaleBOT
#

Project ID: 5920265d-219c-411b-9a8d-028abb72d220

fervent elbow
#

5920265d-219c-411b-9a8d-028abb72d220

hollow spire
#

it would be much easier if you could provide your repo?

#

also, for future reference you are missing a start command, and theres no need for using pm2 on railway

meager cobalt
#

see if there is the word "leech" anywhere in ur code

fervent elbow
meager cobalt
#

well there's the problem

fervent elbow
meager cobalt
#

railway doesn't check actual dependencies, it checks for if the repo contains a certain word

#

i think ud need to get a team member to whitelist ur repo

fervent elbow
#

Ahh okay, so how do I proceed?

hollow spire
hollow spire
fervent elbow
fervent elbow
hollow spire
#

does it absolutely need to be private, and if so, why?

fervent elbow
#

Who do I approach for the whitelisting though?

fervent elbow
#

But I can make some adjustments if it's necessary

hollow spire
#

okay then that makes it much easier

#

easy peasy

fervent elbow
#

Ah okay makes sense. So no other way to handle this than to upgrade to team plan? I have a developer plan already though

hollow spire
undone quail
undone quail
#

Yes

meager cobalt
undone quail
#

Ah I misread, I saw the req.txt at the top and thought it was a dependency. The team will be able to give you an exception for sure then, but you still should be on the teams plan

#

Given that you're using the service commercially, the teams plan is required

fervent elbow
#

Okay I understand the solution. Thanks guys for your help. Much appreciated.

undone quail
#

Happy to help

fervent elbow
#

Hey there, I have tried contacting the team but not getting a response regarding this issue. Might know any other way to reach out to them other than the email?

hollow spire
#

you could have removed the word by now lol

fervent elbow
fervent elbow
nimble minnow
#

and then decode it

hollow spire
meager cobalt
#

._.

#

so ur telling them to monkeypatch instead of getting the actual problem done

hollow spire
#

no we are both joking

meager cobalt
#

...

nimble minnow
#

I mean I included a trollface so

#

I thought it was pretty clear

hollow spire
#

they just have to wait for a team member to answer their email in the coming weekdays, nothing we can do

nimble minnow
#

nothing we can do

undone quail
#

They sent an email on Friday (a holiday in NA), the US has a holiday on Monday afaik

#

You'll have to wait

nimble minnow
#

the team is celebrating not working by not working

fervent elbow
#

I am still waiting though

#

lol

hollow spire
#

though my advice still stands, upgrade to teams account for direct support from the team

fervent elbow
hollow spire
#

you have clients, it's recommended you be on the teams account anyway, but that's all I'll say and I'll let the team enforce that

hollow spire
fervent elbow
#

I have no problem upgrading but I am worried if it would still be the same after upgrading and if they still won't respond

fervent elbow
#

I will upgrade now and see if that solves the problem

hollow spire
#

don't expect instant responses though, they are still a team of something like 15 supporting a userbase of what 500k users?

#

you will have to show your codebase to them obviously, and having to add them to your private repo is not going to speed up the process for you

fervent elbow
#

Not a big problem to temporarily make the repo public.

#

But let's get the upgrade first

hollow spire
#

perfect, do that before you email them so that there's less back and forth

#

and I'd also just like to state that I'm making no guarantees what-so-ever on if the team will whitelist your repo, they might find it risky for other reasons and deny your request, just a little disclaimer from me

fervent elbow
#

Yeah that's something I need to worry about too. Thanks man

hollow spire
#

no problem, I wish you success!

fervent elbow
#

I have upgraded to teams plan now, how do I get access to the private channel now?

tawny whaleBOT
#

Flagging this thread. A team member will be with you shortly.

fervent trellisBOT
#

Hey there, I can make that channel for you right now!

#

Sorry for the delay