@azure/core-xml
Core library for interacting with XML payloads
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:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper declared as a dependency; phantom-dep detection is a false positive for TypeScript-compiled Azure SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Azure SDK packages routinely publish at non-1.0.0 versions reflecting monorepo maturity, and README links are standard Azure SDK documentation. Not a spam/phishing indicator. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 2 / 13 | |
| 1.5.0 | 2 / 10 | |
| 1.4.5 | 2 / 10 | |
| 1.4.4 | 2 / 12 | |
| 1.4.3 | 2 / 13 | |
| 1.4.2 | 2 / 14 | |
| 1.4.1 | 2 / 14 | |
| 1.4.0 | 2 / 14 | |
| 1.3.4 | 2 / 30 | |
| 1.3.3 | 2 / 32 | |
| 1.3.2 | 2 / 32 | |
| 1.3.1 | 2 / 32 | |
| 1.3.0 | 2 / 31 | |
| 1.2.1 | 2 / 30 | |
| 1.2.0 | 2 / 31 | |
| 1.1.0 | 2 / 32 | |
| 1.0.0 | 2 / 33 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.