@smithers-orchestrator/gateway-ui
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is an in-org sibling package, not a third-party supply-chain risk. | ai | |
| source-diff | obfuscated-file:src/workflowGraphCss.ts | AI (source-diff): Pre-minified xyflow CSS string bundled at build time, not obfuscated code. | ai | |
| dependencies | unvetted-dep:@smithers-orchestrator/ui | AI (dependencies): First-party sibling package from same monorepo/publisher. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.29.0 | 6 / 8 | |
| 0.28.0 | 4 / 7 | |
| 0.27.0 | 3 / 7 | |
| 0.26.1 | 3 / 7 |
v0.29.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (esbuild) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.