
Research
Supply Chain Attack on Axios Pulls Malicious Dependency from npm
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
@wsdot/bridge-vc
Advanced tools
Not ready for production. Work-in-progress. Instructions may not yet be functional.
npm install @wsdot/bridge-vc
This sample demonstrates using this code via JavaScript Modules. You can also use Webpack (or a similar tool) to bundle your code and the imported modules together to be compatible with more browsers.
index.mjs
This is the code for the demo page's JavaScript Module.
// import functions
import { createControl, fetchCrossingInfo } from "./node_modules/@wsdot/bridge-vc/dist/esm/index.mjs";
// Get crossing location ID URL search parameter.
const urlSearchParams = new URLSearchParams(location.search);
const idString = urlSearchParams.get("id");
const crossingId = parseInt(idString);
// Write error message if ID is invalid.
if (isNaN(crossingId)) {
const p = document.createElement("p");
p.textContent = `invalid crossing id: ${idString}`;
document.body.appendChild(p);
} else {
// Query SOE for crossing location info,
// then create control displaying that info.
const mapServiceUrl =
"https://www.example.com/arcgis/rest/services/Bridge/BridgeVerticalClearance/MapServer";
fetchCrossingInfo(crossingId, mapServiceUrl).then(
result => {
const control = createControl(result);
document.body.appendChild(control);
},
error => {
const p = document.createElement("p");
p.textContent = error.message;
document.body.appendChild(p);
}
);
}
If using webpack and / or TypeScript, the import statement would be slightly different. Only the package name is used, instead of the path to the packages main module script file.
import { createControl, fetchCrossingInfo } from "@wsdot/bridge-vc";
index.html
This is the index page that references the JavaScript Module defined above.
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>Demo</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" href="./node_modules/@wsdot/bridge-vc/verticalclearance.css" />
<link
href="https://fonts.googleapis.com/css?family=Lato|Overpass"
rel="stylesheet"
/>
<link rel="stylesheet" href="index.css" />
</head>
<body>
<script type="module" src="index.mjs"></script>
</body>
</html>
FAQs
Client for Bridge Vertical Clearance map service queries
The npm package @wsdot/bridge-vc receives a total of 3 weekly downloads. As such, @wsdot/bridge-vc popularity was classified as not popular.
We found that @wsdot/bridge-vc 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.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.

Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.