@sjcrh/proteinpaint-front
The web bundle for window.runproteinpaint(). The intent is for this package to contain most of the "porcelain" or "portal-like" features of proteinpaint, such as headers and other elements that are not likely to be shown by an embedder portal.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in CLI init.js bin script for setup commands; expected pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped St. Jude org package with 468 versions; missing keywords/README code blocks are cosmetic, not spam indicators. | ai |
Versions (showing 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 2.197.0 | 0 / 6 | |
| 2.196.0 | 0 / 6 | |
| 2.195.0 | 0 / 6 | |
| 2.194.0 | 0 / 6 | |
| 2.193.0 | 0 / 6 | |
| 2.192.0 | 0 / 6 | |
| 2.191.4 | 0 / 6 | |
| 2.191.3 | 0 / 6 | |
| 2.191.2 | 0 / 6 | |
| 2.191.0 | 0 / 6 | |
| 2.190.2 | 0 / 6 | |
| 2.190.1 | 0 / 6 | |
| 2.190.0 | 0 / 6 | |
| 2.189.0 | 0 / 6 | |
| 2.188.1 | 0 / 6 | |
| 2.188.0 | 0 / 6 | |
| 2.187.0 | 0 / 6 | |
| 2.186.0 | 0 / 6 | |
| 2.185.0 | 0 / 6 | |
| 2.184.0 | 0 / 6 | |
| 2.183.1 | 0 / 6 | |
| 2.183.0 | 0 / 6 | |
| 2.182.1 | 0 / 6 | |
| 2.182.0 | 0 / 6 | |
| 2.181.0 | 0 / 6 | |
| 2.64.0 | 0 / 5 | |
| 2.63.6 | 0 / 5 | |
| 2.63.5 | 0 / 5 | |
| 2.63.4 | 0 / 5 | |
| 2.63.3 | 0 / 5 | |
| 2.63.2 | 0 / 5 | |
| 2.63.1 | 0 / 5 | |
| 2.63.0 | 0 / 5 | |
| 2.62.0 | 0 / 5 | |
| 2.61.2 | 0 / 5 | |
| 2.61.1 | 0 / 5 | |
| 2.61.0 | 0 / 5 | |
| 2.60.0 | 0 / 5 | |
| 2.59.0 | 0 / 5 | |
| 2.58.1 | 0 / 5 | |
| 2.58.0 | 0 / 5 | |
| 2.57.0 | 0 / 5 | |
| 2.55.0 | 0 / 5 | |
| 2.53.0 | 0 / 5 | |
| 2.51.2 | 0 / 5 | |
| 2.51.0 | 0 / 5 | |
| 2.49.0 | 0 / 5 | |
| 2.48.0 | 0 / 5 | |
| 2.47.0 | 0 / 5 | |
| 2.46.3 | 0 / 5 | |
| 2.46.0 | 0 / 5 | |
| 2.45.0 | 0 / 5 | |
| 2.43.1 | 0 / 5 | |
| 2.42.2 | 0 / 5 | |
| 2.41.1 | 0 / 5 | |
| 2.40.8 | 0 / 5 | |
| 2.40.6 | 0 / 5 | |
| 2.40.4 | 0 / 5 | |
| 2.40.2 | 0 / 5 | |
| 2.40.1 | 0 / 5 | |
| 2.39.6 | 0 / 5 | |
| 2.39.4 | 0 / 5 | |
| 2.39.2 | 0 / 5 | |
| 2.39.0 | 0 / 5 | |
| 2.38.0 | 0 / 5 | |
| 2.36.0 | 0 / 5 | |
| 2.35.0 | 0 / 5 | |
| 2.34.0 | 0 / 5 | |
| 2.33.0 | 0 / 5 | |
| 2.32.0 | 0 / 5 | |
| 2.30.5 | 0 / 5 | |
| 2.30.3 | 0 / 5 | |
| 2.30.2 | 0 / 5 | |
| 2.30.0 | 0 / 5 | |
| 2.29.5 | 0 / 5 | |
| 2.29.3 | 0 / 5 | |
| 2.29.1 | 0 / 5 | |
| 2.27.0 | 0 / 5 | |
| 2.26.0 | 0 / 5 | |
| 2.24.0 | 0 / 5 | |
| 2.19.2 | 0 / 5 | |
| 2.18.3 | 0 / 5 | |
| 2.18.1 | 0 / 5 | |
| 2.16.0 | 0 / 5 | |
| 2.14.4 | 0 / 5 | |
| 2.14.2 | 0 / 5 | |
| 2.14.1 | 0 / 5 | |
| 2.13.0 | 0 / 5 | |
| 2.12.0 | 0 / 5 |
v2.197.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.196.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.195.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.194.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.193.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.