@servicenow/sdk-build-core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used inside a Proxy handler in taxonomy.ts — standard TypeScript pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:xmlbuilder2 | AI (phantom-deps): xmlbuilder2 is explicitly listed in package.json dependencies; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.7.2 | 15 / 2 | |
| 4.7.1 | 15 / 2 | |
| 4.7.0 | 15 / 2 | |
| 4.6.1 | 15 / 2 | |
| 4.5.0 | 15 / 2 | |
| 4.4.1 | 15 / 3 | |
| 4.4.0 | 15 / 3 | |
| 4.3.0 | 15 / 3 | |
| 4.2.0 | 14 / 3 | |
| 4.1.1 | 14 / 3 | |
| 4.1.0 | 14 / 3 | |
| 4.0.2 | 14 / 3 | |
| 4.0.1 | 14 / 3 | |
| 4.0.0 | 13 / 3 |
v4.7.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (phaniprakash) than the most recent previously approved version (gouthami.pantangi) on 2026-06-05, but phaniprakash is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (phaniprakash) than the most recent previously approved version (kayleigh.french) on 2025-11-21, but phaniprakash is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.