@spark-ui/cli-utils
Spark CLI utils
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is a known implicit/binary dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra referenced in config files; stable false positive for this package. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 17.15.0 | 7 / 3 | |
| 17.14.4 | 7 / 3 | |
| 17.14.3 | 7 / 3 | |
| 17.14.2 | 7 / 3 | |
| 17.14.1 | 7 / 3 | |
| 17.14.0 | 7 / 3 | |
| 17.13.2 | 7 / 3 | |
| 17.13.1 | 7 / 3 | |
| 17.13.0 | 7 / 3 | |
| 17.12.0 | 7 / 3 | |
| 17.11.3 | 7 / 3 | |
| 17.11.2 | 7 / 3 | |
| 17.11.1 | 7 / 3 | |
| 17.11.0 | 7 / 3 | |
| 17.10.4 | 7 / 3 | |
| 17.10.3 | 7 / 3 | |
| 17.10.2 | 7 / 3 | |
| 17.10.1 | 7 / 3 | |
| 17.10.0 | 7 / 3 | |
| 17.9.3 | 7 / 3 | |
| 17.9.2 | 7 / 3 | |
| 17.9.1 | 7 / 3 | |
| 17.9.0 | 7 / 3 | |
| 17.8.0 | 7 / 3 | |
| 17.7.0 | 7 / 3 | |
| 17.6.1 | 7 / 3 | |
| 17.6.0 | 7 / 3 | |
| 17.5.7 | 7 / 3 | |
| 17.5.6 | 7 / 3 | |
| 17.5.5 | 7 / 3 | |
| 17.5.4 | 7 / 3 | |
| 17.5.3 | 7 / 3 | |
| 17.5.2 | 7 / 3 | |
| 17.5.1 | 7 / 3 | |
| 17.5.0 | 7 / 3 | |
| 17.4.2 | 7 / 3 | |
| 17.4.1 | 7 / 3 | |
| 17.4.0 | 7 / 3 | |
| 17.3.2 | 7 / 3 | |
| 17.3.1 | 7 / 3 | |
| 17.3.0 | 7 / 3 | |
| 17.2.5 | 7 / 3 | |
| 17.2.4 | 7 / 3 | |
| 17.2.3 | 7 / 3 | |
| 17.2.2 | 7 / 3 | |
| 17.2.1 | 7 / 3 | |
| 17.2.0 | 7 / 3 | |
| 17.1.1 | 7 / 3 | |
| 17.1.0 | 7 / 3 | |
| 17.0.1 | 7 / 3 | |
| 17.0.0 | 7 / 3 | |
| 16.2.3 | 7 / 3 | |
| 16.2.2 | 7 / 3 | |
| 16.2.1 | 7 / 3 | |
| 16.2.0 | 7 / 3 | |
| 16.1.0 | 7 / 3 | |
| 16.0.3 | 7 / 3 | |
| 16.0.2 | 7 / 3 | |
| 16.0.1 | 7 / 3 | |
| 16.0.0 | 7 / 3 | |
| 15.1.0 | 7 / 3 | |
| 15.0.0 | 7 / 3 | |
| 14.1.2 | 7 / 3 | |
| 14.1.1 | 7 / 3 | |
| 14.1.0 | 7 / 3 | |
| 14.0.0 | 7 / 3 | |
| 13.2.0 | 7 / 3 | |
| 13.1.5 | 7 / 3 | |
| 13.1.4 | 7 / 3 | |
| 13.1.3 | 7 / 3 | |
| 13.1.2 | 7 / 3 | |
| 13.1.1 | 7 / 3 | |
| 13.1.0 | 7 / 1 | |
| 13.0.7 | 7 / 1 | |
| 13.0.6 | 7 / 1 | |
| 13.0.5 | 7 / 1 | |
| 13.0.4 | 7 / 1 | |
| 13.0.3 | 7 / 1 | |
| 13.0.2 | 7 / 1 | |
| 13.0.1 | 7 / 1 | |
| 12.2.0 | 7 / 1 | |
| 12.1.2 | 7 / 1 | |
| 12.1.1 | 7 / 1 | |
| 12.1.0 | 7 / 1 | |
| 12.0.1 | 7 / 1 | |
| 12.0.0 | 7 / 1 | |
| 11.7.1 | 7 / 1 | |
| 11.7.0 | 7 / 1 | |
| 11.6.1 | 7 / 1 | |
| 11.6.0 | 7 / 1 | |
| 11.5.1 | 7 / 1 | |
| 11.5.0 | 7 / 1 | |
| 11.4.3 | 7 / 1 | |
| 11.4.2 | 7 / 1 | |
| 11.4.1 | 7 / 1 | |
| 11.4.0 | 7 / 1 | |
| 11.3.1 | 7 / 1 | |
| 11.3.0 | 7 / 1 | |
| 11.2.5 | 7 / 1 | |
| 11.2.4 | 7 / 1 |
v17.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.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 (powerplex) than the most recent previously approved version (andresin87) on 2026-03-31, but powerplex 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.
v17.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
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 (powerplex) than the most recent previously approved version (andresin87) on 2025-12-12, but powerplex 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.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.