pb-node | Pandorabots API module for Node.js

There's a lot of info here and I'm not sure it's all relevant. It seems that the crux of your problem is that when your application is staged (i.e. when the buildpack runs), the buildpack runs npm install which in turn tries to grab a dependency from a private github repo.

Assuming I've got that correct...

1. One possible solution would be to vendor your dependencies. When you "vendor" dependencies, you're basically running npm install locally or in some environment you control, then you're sending the dependencies up with your application to Cloud Foundry. It makes for a larger application, but when your application stages and the platform runs npm install all the dependencies exist already so npm install becomes basically a no-op.

   The main trick is with compiled dependencies. To make this work, you need to vendor your dependencies on a system that matches the rootfs on Cloud Foundry. Currently the cflinuxfs2 stack matches Ubuntu Trusty 14.04.

   You can read more about vendoring dependencies in the docs here.

   https://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring

2. Another solution would be to use cf local. This is a cf cli plugin that uses Docker to run buildpacks on your local system. On the local system, you'd presumably be able to access your private repository (it's basically running from your laptop/PC). The buildpack would then run and create a completely self-contained droplet. You can then use cf local to export that droplet & send it to any other Cloud Foundry platform.

   The beauty is that the droplet is everything that's needed for the platform to run your app, so it doesn't even need to stage your application which bypasses the who problem of accessing your private code from the staging environment on the public Cloud Foundry.

3. The other thing you might be able to do, and I'm not 100% sure this will work, is to include a .npmrc file. The buildpack should configure npm to look at this file when it runs npm install. The idea here would be to include some configuration option to npm that would allow it to connect to your repo. I'm not an expert with npm though, so I don't know if such an option exists. Just thought I'd mention this in case it might help.