@rcsb/rcsb-saguaro-app
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/app.js | AI (source-diff): Standard webpack bundle output with LICENSE banner, not obfuscation. | ai | |
| source-diff | net-exec-file:build/app.js | AI (source-diff): Bundled webapp code (workbox/service-worker patterns), no malicious exfil target. | ai | |
| phantom-deps | phantom-dep:@rcsb/rcsb-search-tools | AI (phantom-deps): Same-org package, expected usage pattern. | ai | |
| phantom-deps | phantom-dep:@rcsb/rcsb-charts | AI (phantom-deps): Same-org package, expected usage pattern. | ai | |
| phantom-deps | phantom-dep:@rcsb/rcsb-saguaro | AI (phantom-deps): Same-org core dependency, false positive pattern. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Config-referenced, not malicious; standard peer lib. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): UI dep used via config/build, false positive pattern. | ai | |
| phantom-deps | phantom-dep:react-bootstrap | AI (phantom-deps): UI dep used via config/build, false positive pattern. | ai | |
| phantom-deps | phantom-dep:string-to-color | AI (phantom-deps): Utility dep, false positive pattern. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Bootstrap is a CSS framework commonly referenced in config/SCSS without direct JS imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ideogram | AI (phantom-deps): ideogram is a declared runtime dep used via webpack/config; phantom-dep is a stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.7.0 | 12 / 32 | |
| 6.6.1 | 12 / 32 | |
| 6.6.0 | 12 / 32 | |
| 6.5.0 | 12 / 32 | |
| 6.4.8 | 12 / 36 | |
| 6.4.7 | 12 / 36 | |
| 6.4.6 | 12 / 36 | |
| 6.4.5 | 12 / 36 | |
| 6.3.4 | 8 / 39 | |
| 3.1.1 | 4 / 27 |
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.7
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.6
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.5
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
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 (sebastian.bittrich) than the most recent previously approved version (bioinsilico) on 2025-01-14, but sebastian.bittrich 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.