relaxed-json
Relaxed JSON is strict superset JSON, relaxing strictness of valilla JSON
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:components/jquery-2.0.3.js | AI (source-diff): This is the canonical jQuery 2.0.3 library bundled as a demo/documentation asset. The net+exec pattern is inherent to jQuery's design and poses no malware risk in this context. | ai | |
| source-diff | net-exec-file:components/underscore.js | AI (source-diff): This is the canonical Underscore.js 1.5.2 vendored library. The 'network' signal is a URL in a comment header; the code execution is Underscore's template engine. Not malicious. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() usage is in Underscore.js 1.5.2's template engine — a well-known, documented pattern in that library, not a security concern for this package. | ai | |
| source-diff | net-exec-file:web/lib/jquery-2.0.3.js | AI (source-diff): This is the canonical jQuery 2.0.3 library bundled in the package's web demo directory, not a runtime dependency. The pattern is benign for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 2 / 7 | |
| 1.0.2 | 2 / 9 | |
| 1.0.1 | 2 / 9 | |
| 1.0.0 | 2 / 9 | |
| 0.2.9 | 2 / 8 | |
| 0.2.8 | 2 / 8 | |
| 0.2.7 | 2 / 7 | |
| 0.2.6 | 0 / 6 | |
| 0.2.4 | 0 / 6 | |
| 0.2.3 | 0 / 6 | |
| 0.2.2 | 0 / 6 | |
| 0.2.1 | 0 / 8 | |
| 0.2.0 | 0 / 8 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.