@rcsb/rcsb-molstar
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:build/dist/viewer/rcsb-molstar.js | AI (source-diff): Webpack bundle of minified library code, not true obfuscation; no diff vs prior approved version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Established RCSB/molstar project org change, publisher has long clean track record. | ai | |
| dependencies | unvetted-dep:molstar | AI (dependencies): molstar is the core upstream library this package explicitly wraps; dependency is expected and stable. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped TypeScript type package; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework-scoped TypeScript type package; not directly imported by convention. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.14.4 | 7 / 21 | |
| 2.14.3 | 7 / 21 | |
| 2.14.2 | 7 / 21 | |
| 2.14.1 | 7 / 21 | |
| 2.14.0 | 7 / 21 |
v2.14.3
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.