
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
interactive-mock-server
Advanced tools
Mock Server that can be configured interactively in real-time!
An mock server that allows you to dynamically adjust mock endpoints in real-time!
Almost all mock server implementations provide the option to specify mock routes/endpoints beforehande, but they don't allow you to dynamically adjust those routes after a certain amount of time. While those implementations are geared toward CI environment testing, manual testing of you app is also important.
How your app responds to different responses requires a type of exploration that other mock servers don't have. The ability to adjust a route's response dynamically allows you to test how the app responds to different responses from the same route over time. This also allows you to explore how the app responds to unexpected responses without having to copy boilerplate code, adjust one small part (such as the the status code) and restart the server.
Instead this mock server provides an interactive way of adjusting simple parts of the mocked response without having to stop and start the mock server over and over.
Once the server is started (see instructions on running below), You can navigate to the
dashboard page /__dashboard. This route exists as a way to prevent conflicts with other
potential mock endpoints. From this page, you can view endpoints (/__dashboard/endpoints),
create a new endpoint (/__dashboard/endpoints/new) or view/edit an existing endpoint
(/__dashboard/endpoints/:id).
Once an endpoint has been created, it will be automatically enabled on the mock server.
Instructions TBD! (You can use the contributing instructions for running in dev mode at this time)
yarn installyarn run buildyarn run dev:apphttp://localhost:9000/__dashboard)Created mock endpoints are available from the same base: http://localhost:9000/
Repeat steps 1-4 above and
yarn run dev:webhttp://localhost:9100/__dashboard)NOTE: The mock server must also be running in a separate terminal (Step 4). The dashboard uses several API methods from the mock server that are automatically proxied to the mock server.
ALSO NOTE: All created mock endpoints will be available using the mock server, NOT the webpack dev server. You will have to go to
http://localhost:9000instead ofhttp://localhost:9100to test the mock endpoints created
FAQs
Mock Server that can be configured interactively in real-time!
We found that interactive-mock-server 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.