xml-js
A convertor between XML text and Javascript object / JSON text.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; publisher is the original author with a clean track record over 3621 days. | ai | |
| source-diff | net-exec-file:test/browse-jasmine/lib/jasmine-2.5.0/jasmine.js | AI (source-diff): Standard Jasmine 2.5.0 test framework bundle (Pivotal Labs, MIT). Test-only asset, not runtime code. Network+exec patterns are normal for test frameworks. | ai | |
| source-diff | net-exec-file:test/browse-jasmine/lib/jasmine-2.5.2/jasmine.js | AI (source-diff): This is the standard Jasmine 2.5.2 test framework library (from Pivotal Labs) bundled for browser test running. Not malicious. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in vendored Jasmine test framework code, not in the package's runtime library. Standard Jasmine pattern. | ai | |
| source-diff | net-exec-file:jasmine/lib/jasmine-2.5.0/jasmine.js | AI (source-diff): Standard Jasmine 2.5.0 test framework library (Pivotal Labs); not runtime code. Network+exec pattern is Jasmine internals. | ai | |
| source-diff | net-exec-file:dist/xml-js.js | AI (source-diff): Standard webpack bundle output for browser distribution; dynamic require and module.call are webpack boilerplate, not malicious network/exec patterns. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from adding webpack dist bundles for browser use; consistent with the new build script. | ai | |
| source-diff | net-exec-file:dist/xml-js.min.js | AI (source-diff): Minified webpack bundle of the same library; same false positive as the unminified version. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.6.11 | 1 / 25 | |
| 1.6.10 | 1 / 25 | |
| 1.6.9 | 1 / 25 | |
| 1.6.8 | 1 / 25 | |
| 1.6.7 | 1 / 25 | |
| 1.6.6 | 1 / 25 | |
| 1.6.5 | 1 / 25 | |
| 1.6.4 | 1 / 25 | |
| 1.6.3 | 1 / 25 | |
| 1.6.2 | 1 / 25 | |
| 1.6.1 | 1 / 17 | |
| 1.6.0 | 1 / 16 | |
| 1.5.2 | 1 / 14 | |
| 1.5.1 | 1 / 14 | |
| 1.5.0 | 1 / 14 | |
| 1.4.2 | 1 / 14 | |
| 1.4.1 | 1 / 14 | |
| 1.4.0 | 1 / 14 | |
| 1.3.4 | 1 / 14 | |
| 1.3.3 | 1 / 14 | |
| 1.3.2 | 1 / 14 | |
| 1.3.1 | 1 / 14 | |
| 1.3.0 | 1 / 14 | |
| 1.2.2 | 1 / 14 | |
| 1.2.1 | 1 / 14 | |
| 1.2.0 | 1 / 14 | |
| 1.1.0 | 1 / 14 | |
| 1.0.2 | 1 / 15 | |
| 1.0.1 | 1 / 15 | |
| 1.0.0 | 1 / 15 | |
| 0.9.7 | 1 / 14 | |
| 0.9.6 | 1 / 14 | |
| 0.9.5 | 1 / 14 | |
| 0.9.4 | 1 / 14 | |
| 0.9.3 | 1 / 16 | |
| 0.9.2 | 1 / 16 | |
| 0.9.1 | 1 / 16 | |
| 0.9.0 | 1 / 16 | |
| 0.8.9 | 1 / 17 | |
| 0.8.8 | 1 / 17 | |
| 0.8.7 | 1 / 17 | |
| 0.8.6 | 1 / 17 | |
| 0.8.5 | 1 / 17 | |
| 0.8.4 | 1 / 17 | |
| 0.8.3 | 1 / 17 | |
| 0.8.2 | 1 / 17 | |
| 0.8.1 | 1 / 17 | |
| 0.8.0 | 1 / 17 | |
| 0.1.0 | 1 / 16 |
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.6.2
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
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.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
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.9.5
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.9.4
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.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage 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.