
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
apigee-remote-proxy
Advanced tools
A Proxy that installs on Apigee Edge to expose key pieces of Apigee functionality to remote systems via a REST API.
By deploying the Apigee Remote Proxy to Apigee, you can run code locally that communicates with Apigee in the cloud. To do this, you deploy a special API proxy to the cloud, which gives you a dedicated API that your local server can use to invoke various Apigee functions like Quota, Cache, OAuth, Analytics, and the like.
The easiest way to provision the proxy to Apigee and to use the Node.js functionality is to use this module:
npm install -g apigee-remote-proxy
This will install apigee-remote-proxy on your local system so that you can run "deployApigeeRemoteProxy" from your path at any time.
If you don't have your own installation of Apigee Enterprise, or don't have an Apigee Edge Account, then go to Apigee Enterprise and make one. You'll need to know three things:
You can now deploy the proxy to your environment using deployApigeeRemoteProxy like this:
deployApigeeRemoteProxy -b https://api.enterprise.apigee.com -o ORGANIZATION -u USERNAME -p PASSWORD -e ENVIRONMENT
NOTE: Replace ORGANIZATION, USERNAME, PASSWORD, and ENVIRONMENT with your Apigee account info.
Alternatively, you may omit and or all the parameters and deployApigeeRemoteProxy will prompt you for them.
Once the proxy had been deployed, then you can invoke the proxy at the URL:
https://ORGANIZATION-test.apigee.net/apigee-remote-proxy
(Replace ORGANIZATION with your Apigee organization name)
If you access this URL right now, you should get a 401 (Unauthorized) error because you didn't supply an API key. (If deployment failed, you will get a 404.)
FAQs
A Proxy that installs on Apigee Edge to expose key pieces of Apigee functionality to remote systems via a REST API.
The npm package apigee-remote-proxy receives a total of 3 weekly downloads. As such, apigee-remote-proxy popularity was classified as not popular.
We found that apigee-remote-proxy demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.