![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
The NodeJS implementation to access the OWASP ZAP API. For more information about OWASP ZAP consult the (main) OWASP ZAP project.
npm install zaproxy
By default ZAP requires an API key to be sent with every request. This is done automatically providing you supply the same API key when you instantiate the ZapClient
that you use to run ZAP with. All following API requests will use this same API key.
You can disable the API key when running ZAP if you are on a trusted network and understand the risks. If you choose to do so, you may omit the apiKey
property of the zapOptions
object supplied to ZapClient
.
const ZapClient = require('zaproxy');
const zapOptions = {
apiKey: 'eahhr6h6kal92j21gkcnhkp80t',
proxy: {
host: '127.0.0.1',
port: 8080,
},
};
const zaproxy = new ZapClient(zapOptions);
let params = {
contextid: contextid,
userid: userid,
url: sutbaseurl,
maxchildren: maxchildren,
recurse: recurse,
subtreeonly: subtreeonly,
};
let response = await zaproxy.spider.scanAsUser(params);
console.log(response);
For a full API list, see https://github.com/zaproxy/zaproxy/wiki/ApiGen_Index.
The Node API methods have the same signature as the API documentation, featuring both callback and promise based interfaces, making everyone happy.
The API key is no longer explicitly required on any Node API method invocations. Unless you have disabled the API key when running ZAP, simply provide it on Node API instantiation as mentioned in the Usage section and it will be provided automatically with each request to the ZAP API.
For help using the OWASP ZAP API refer to:
To report issues related to the OWASP ZAP Node API, bugs and enhancements requests, use the issue tracker of this project.
[2.0.0-rc.1] - 2023-05-19
FAQs
ZAP API Client for Node.js
The npm package zaproxy receives a total of 0 weekly downloads. As such, zaproxy popularity was classified as not popular.
We found that zaproxy demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.