
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
Various utilities for JSON References (http://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03).
Various utilities for JSON References, and JSON Pointers since JSON References are part JSON Pointer.
All examples below use a variable called jsonRefs. Here is how to create it:
var jsRefs = require('jsonRefs');
findRefs (json)Arguments
json {object} - The JavaScript object to search for referencesResponse
An object whose keys are JSON Pointers to where the JSON Reference's $ref node is and the JSON Reference string.
pathFromPointer (ptr)Arguments
ptr {string} - A JSON Pointer stringResponse
A string[] of path segments for the JSON Pointer unless its a remote reference in which case ptr is returned as-is.
Example
console.log(jsonRefs.pathFromPointer('#/owner/login')); // ['owner', 'login']
pathToPointer (path)Arguments
path {string[]} - An array of path segments.Response
A string representing a JSON Pointer.
Example
console.log(jsonRefs.pathToPointer(['owner', 'login'])); // #/owner/login
resolveRefs (json, done)Arguments
json {object}: The JavaScript object containing zero or more JSON Referencesdone {function}: An error-first callback to be called with the fully-resolved objectResponse
If there is an Error, the callback is called with the Error in the first argument and undefined in the second
argument. If there is no Error, the first argument is undefined and the second argument is an object whose value
is the fully resolved document.
Example
var json = {
name: 'json-refs',
owner: {
$ref: 'https://api.github.com/repos/whitlockjc/json-refs#/owner'
}
};
jsonRefs.resolveRefs(json, function (err, rJson) {
if (err) throw err;
console.log(JSON.stringify(rJson)); // {name: 'json-refs', owner: {/* GitHub Repository Owner Information */}}
});
Swagger Parser is a package that can parse, validate, and dereference Swagger and OpenAPI documents. Similar to json-refs, it handles resolving references but is specifically tailored for Swagger and OpenAPI specs, providing more specialized functionality in these contexts compared to the more general-purpose json-refs.
This package dereferences JSON Schema $refs pointers. Like json-refs, it resolves references within JSON documents but focuses specifically on JSON Schema, making it ideal for scenarios involving JSON Schema validation and manipulation.
FAQs
Various utilities for JSON References (http://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03).
The npm package json-refs receives a total of 799,752 weekly downloads. As such, json-refs popularity was classified as popular.
We found that json-refs 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
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.