← Home

@servicenow/sdk-build-plugins

12
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mdwraggnow-buildcuong.transdivatiahuichuanchaitanyababukayleigh.frenchdwong-servicenowpooja.chamarthigouthami.pantangiphaniprakashrajavenkatesh.servicenowmanishroy-servicenowsavya.allakrishnakr1989richa.srivastavaaprameya.vjyothsna.kilari

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/flow/utils/built-in-complex-objects.js AI (source-diff): File contains serialized JSON schema metadata for ServiceNow Flow Designer built-ins, not obfuscated/malicious code. ai
semgrep semgrep:base64-decode AI (semgrep): Pattern is gunzip+JSON parse of compressed input data, not payload decoding or obfuscation. ai
phantom-deps phantom-dep:libxmljs2 AI (phantom-deps): libxmljs2 is an optional dependency; not directly imported is expected for optional native bindings. ai
phantom-deps phantom-dep:jsonschema AI (phantom-deps): Config-file reference pattern is a stable false positive for this build-plugins package. ai

Versions (showing 12 of 12)

Version Deps Published
4.7.2 20 / 2
4.7.1 20 / 2
4.7.0 20 / 2
4.6.1 20 / 2
4.4.1 19 / 3
4.4.0 18 / 3
4.2.0 20 / 3
4.1.1 21 / 3
4.1.0 19 / 3
4.0.2 19 / 3
4.0.1 19 / 3
4.0.0 19 / 3

v4.7.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: gouthami.pantangi → phaniprakash (on 2026-06-05, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.4.1

2 findings
HIGH New obfuscated file: dist/flow/utils/built-in-complex-objects.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

2 findings
HIGH New obfuscated file: dist/flow/utils/built-in-complex-objects.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: phaniprakash → richa.srivastava (on 2025-12-10, known maintainer) provenance

This version was published by a different npm account (richa.srivastava) than the most recent previously approved version (phaniprakash) on 2025-12-10, but richa.srivastava 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.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.