@jupyterlab/tooltip
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): JupyterLab migrated release automation from jupyterlab-release-bot to GitHub Actions with SLSA provenance. This transition is legitimate and expected for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 428 versions; dormancy is a per-sub-package artifact of the JupyterLab monorepo release cadence, not actual abandonment. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; short README and missing keywords are expected for @jupyterlab/* component packages. | ai |
Versions (showing 26 of 126)
| Version | Deps | Published |
|---|---|---|
| 3.1.12 | 7 / 3 | |
| 3.1.11 | 7 / 3 | |
| 3.1.10 | 7 / 3 | |
| 3.1.9 | 7 / 3 | |
| 3.1.8 | 7 / 3 | |
| 3.1.7 | 7 / 3 | |
| 3.1.6 | 7 / 3 | |
| 3.1.5 | 7 / 3 | |
| 3.1.4 | 7 / 3 | |
| 3.1.3 | 7 / 3 | |
| 3.1.2 | 7 / 3 | |
| 3.1.1 | 7 / 3 | |
| 3.1.0 | 7 / 3 | |
| 3.0.12 | 7 / 3 | |
| 3.0.11 | 7 / 3 | |
| 3.0.10 | 7 / 3 | |
| 3.0.9 | 7 / 3 | |
| 3.0.8 | 7 / 3 | |
| 3.0.7 | 7 / 3 | |
| 3.0.6 | 7 / 3 | |
| 3.0.5 | 7 / 3 | |
| 3.0.4 | 7 / 3 | |
| 3.0.3 | 7 / 3 | |
| 3.0.2 | 7 / 3 | |
| 3.0.1 | 7 / 3 | |
| 3.0.0 | 7 / 3 |
v3.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.