@servicenow/sdk-api
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/external-plugins/flow.js | AI (source-diff): Bundled build output of @servicenow/fluent-flow plugin, not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/external-plugins/flow.js | AI (source-diff): Same bundled plugin file; net+exec calls are legitimate build-tool code, not a dropper. | ai | |
| provenance | no-provenance | AI (provenance): ServiceNow org package; provenance absence is consistent across all versions and not a risk signal here. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars 4.7.9 is a well-known templating library; no active advisories at this version. | ai | |
| dependencies | unvetted-dep:@servicenow/sdk-build-plugins | AI (dependencies): First-party ServiceNow SDK sibling package; stable pattern across SDK releases. | ai | |
| dependencies | unvetted-dep:@servicenow/sdk-build-core | AI (dependencies): First-party ServiceNow SDK sibling package; stable pattern across SDK releases. | ai | |
| dependencies | unvetted-dep:@servicenow/isomorphic-rollup | AI (dependencies): First-party ServiceNow build tooling; consistent with SDK ecosystem. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.9.2 | 11 / 11 | |
| 4.9.1 | 11 / 11 | |
| 4.9.0 | 10 / 11 | |
| 4.7.2 | 9 / 8 | |
| 4.7.0 | 9 / 8 | |
| 4.6.1 | 9 / 8 | |
| 4.6.0 | 9 / 8 | |
| 4.5.0 | 9 / 8 |
v4.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pooja.chamarthi) than the most recent previously approved version (gouthami.pantangi) on 2026-07-17, but pooja.chamarthi 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.