@jupyterlab/markdownviewer
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 is a documented, legitimate transition for the jupyterlab org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): JupyterLab is a monorepo; individual sub-packages like markdownviewer may have long gaps between patch releases while the project remains active. Not indicative of takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sub-packages in large monorepos (like jupyterlab) typically lack standalone README code blocks and keywords. Not a spam/bogus signal for this package. | ai |
Versions (showing 27 of 127)
| Version | Deps | Published |
|---|---|---|
| 3.1.12 | 8 / 3 | |
| 3.1.11 | 8 / 3 | |
| 3.1.10 | 8 / 3 | |
| 3.1.9 | 8 / 3 | |
| 3.1.8 | 8 / 3 | |
| 3.1.7 | 8 / 3 | |
| 3.1.6 | 8 / 3 | |
| 3.1.5 | 8 / 3 | |
| 3.1.4 | 8 / 3 | |
| 3.1.3 | 8 / 3 | |
| 3.1.2 | 8 / 3 | |
| 3.1.1 | 8 / 3 | |
| 3.1.0 | 8 / 3 | |
| 3.0.13 | 8 / 3 | |
| 3.0.12 | 8 / 3 | |
| 3.0.11 | 8 / 3 | |
| 3.0.10 | 8 / 3 | |
| 3.0.9 | 8 / 3 | |
| 3.0.8 | 8 / 3 | |
| 3.0.7 | 8 / 3 | |
| 3.0.6 | 8 / 3 | |
| 3.0.5 | 8 / 3 | |
| 3.0.4 | 8 / 3 | |
| 3.0.3 | 8 / 3 | |
| 3.0.2 | 8 / 3 | |
| 3.0.1 | 8 / 3 | |
| 3.0.0 | 8 / 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.13
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.