@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 — 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 |
|---|---|---|---|---|
| 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-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 | |
| dependencies | unvetted-dep:@servicenow/sdk-build-plugins | AI (dependencies): First-party ServiceNow SDK sibling package; stable pattern across SDK releases. | ai |
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.6.0
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.