@esposter/xml2js
Simple XML to JavaScript object converter.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:sax | AI (phantom-deps): sax is a declared runtime dep used in the built output; phantom-dep heuristic fires on source scan but not on dist. | ai | |
| phantom-deps | phantom-dep:xmlbuilder2 | AI (phantom-deps): xmlbuilder2 is a declared runtime dep used in the built output; same false-positive pattern as sax. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.27.0 | 3 / 8 | |
| 2.26.0 | 3 / 8 | |
| 2.25.0 | 3 / 6 | |
| 2.24.0 | 3 / 3 | |
| 2.23.0 | 3 / 2 | |
| 2.22.0 | 3 / 2 | |
| 2.21.0 | 3 / 2 | |
| 2.20.0 | 3 / 3 | |
| 2.19.2 | 3 / 3 | |
| 2.18.2 | 2 / 2 | |
| 2.17.0 | 2 / 2 | |
| 2.16.0 | 2 / 2 | |
| 2.15.1 | 2 / 2 | |
| 2.15.0 | 2 / 2 | |
| 2.14.0 | 2 / 2 | |
| 2.13.1 | 2 / 2 | |
| 2.13.0 | 2 / 2 | |
| 2.12.0 | 2 / 2 | |
| 2.11.0 | 2 / 2 | |
| 2.10.0 | 2 / 2 | |
| 2.9.0 | 2 / 2 | |
| 2.8.1 | 2 / 2 | |
| 2.8.0 | 2 / 2 | |
| 2.7.0 | 2 / 2 | |
| 2.6.0 | 2 / 2 | |
| 2.5.0 | 2 / 2 | |
| 2.4.1 | 2 / 2 | |
| 2.4.0 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.1 | 2 / 2 |
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.