@jupyterlab/apputils
JupyterLab - Application Utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jupyterlab/coreutils | AI (phantom-deps): Same org scope (@jupyterlab); likely used indirectly or re-exported. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/sanitize-html | AI (phantom-deps): Type-only dependency used at compile time, not directly imported at runtime; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@types/sanitize-html | AI (dependencies): @types/sanitize-html is a TypeScript type definition package for the already-declared sanitize-html runtime dep; its presence as a dependency is a benign early-TypeScript pattern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): jtpio is a well-known JupyterLab core contributor with 1696 approved packages; publisher change from jasongrout is a legitimate project maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (krassowski, goanpeca, mbektas, loichuder) are known JupyterLab contributors; this is a normal team expansion for an active open-source project. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with a CI/tooling change during maintainer transition; no malware indicators present. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Buffer polyfill is a standard pattern for browser-targeting libraries; declared for build/bundler use. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is uncommon (12% adoption); not a material risk for established JupyterLab package. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a well-known Node.js URL polyfill; phantom detection in config files is a stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Diff is cross-major-branch (3.x vs 4.x); added deps are well-known Lumino/React packages consistent with JupyterLab 3.x dependency surface. Not a suspicious addition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): JupyterLab uses a centralized release bot (jupyterlab-release-bot) for publishing; individual maintainer removals are expected organizational changes, not takeover indicators. | ai | |
| dependencies | unvetted-dep:@jupyterlab/services | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/coreutils | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/observables | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/translation | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/ui-components | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/settingregistry | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/rendermime-interfaces | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/statusbar | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/widgets | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/commands | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/domutils | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/algorithm | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/coreutils | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/messaging | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/signaling | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/disposable | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@lumino/virtualdom | AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/statedb | AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:sanitize-html | AI (dependencies): sanitize-html is a well-known HTML sanitization library; its use in a JupyterLab UI utilities package is legitimate and expected. No advisories affect the pinned range. | ai | |
| bogus-package | bogus-package | AI (bogus-package): JupyterLab monorepo packages always publish at coordinated high semver versions and have minimal sub-package READMEs. These signals are structural false positives for this package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): @types/react is intentionally listed as a runtime dep in JupyterLab packages for type-sharing conventions; not a security concern. | ai |
Versions (showing 100 of 212)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 22 / 9 | |
| 3.2.0 | 22 / 9 | |
| 3.1.18 | 21 / 9 | |
| 3.1.17 | 21 / 9 | |
| 3.1.16 | 21 / 9 | |
| 3.1.15 | 21 / 9 | |
| 3.1.13 | 21 / 9 | |
| 3.1.12 | 21 / 9 | |
| 3.1.11 | 21 / 9 | |
| 3.1.10 | 21 / 9 | |
| 3.1.9 | 21 / 9 | |
| 3.1.8 | 21 / 9 | |
| 3.1.7 | 21 / 9 | |
| 3.1.6 | 21 / 9 | |
| 3.1.5 | 21 / 9 | |
| 3.1.4 | 21 / 9 | |
| 3.1.3 | 21 / 9 | |
| 3.1.2 | 21 / 9 | |
| 3.1.1 | 21 / 9 | |
| 3.1.0 | 21 / 9 | |
| 3.0.10 | 22 / 9 | |
| 3.0.9 | 22 / 9 | |
| 3.0.8 | 22 / 9 | |
| 3.0.7 | 22 / 9 | |
| 3.0.6 | 22 / 9 | |
| 3.0.5 | 22 / 9 | |
| 3.0.4 | 22 / 9 | |
| 3.0.3 | 22 / 9 | |
| 3.0.2 | 22 / 9 | |
| 3.0.1 | 22 / 9 | |
| 3.0.0 | 22 / 9 | |
| 2.3.1 | 19 / 9 | |
| 2.3.0 | 19 / 9 | |
| 2.2.7 | 19 / 9 | |
| 2.2.6 | 19 / 9 | |
| 2.2.5 | 19 / 9 | |
| 2.2.4 | 19 / 9 | |
| 2.2.3 | 19 / 9 | |
| 2.2.2 | 19 / 9 | |
| 2.2.1 | 19 / 9 | |
| 2.2.0 | 19 / 9 | |
| 2.1.1 | 19 / 5 | |
| 2.1.0 | 19 / 5 | |
| 2.0.3 | 19 / 5 | |
| 2.0.2 | 19 / 5 | |
| 2.0.1 | 19 / 5 | |
| 2.0.0 | 19 / 5 | |
| 1.2.11 | 17 / 5 | |
| 1.2.10 | 17 / 5 | |
| 1.2.9 | 17 / 5 | |
| 1.2.8 | 17 / 5 | |
| 1.2.7 | 17 / 5 | |
| 1.2.6 | 17 / 5 | |
| 1.2.5 | 17 / 5 | |
| 1.2.4 | 17 / 5 | |
| 1.2.3 | 17 / 5 | |
| 1.2.2 | 17 / 5 | |
| 1.2.1 | 17 / 5 | |
| 1.2.0 | 17 / 5 | |
| 1.1.3 | 17 / 5 | |
| 1.1.2 | 17 / 5 | |
| 1.1.1 | 17 / 5 | |
| 1.1.0 | 17 / 5 | |
| 1.0.5 | 17 / 5 | |
| 1.0.4 | 17 / 5 | |
| 1.0.3 | 17 / 5 | |
| 1.0.2 | 17 / 5 | |
| 1.0.1 | 17 / 5 | |
| 1.0.0 | 17 / 5 | |
| 0.19.1 | 16 / 5 | |
| 0.18.4 | 16 / 4 | |
| 0.18.3 | 16 / 4 | |
| 0.18.2 | 16 / 4 | |
| 0.18.0 | 16 / 4 | |
| 0.17.2 | 16 / 4 | |
| 0.17.1 | 16 / 4 | |
| 0.16.4 | 16 / 4 | |
| 0.16.3 | 16 / 4 | |
| 0.16.2 | 16 / 4 | |
| 0.16.1 | 15 / 5 | |
| 0.16.0 | 16 / 4 | |
| 0.15.5 | 16 / 4 | |
| 0.15.4 | 16 / 4 | |
| 0.15.3 | 16 / 4 | |
| 0.15.2 | 16 / 4 | |
| 0.15.1 | 16 / 4 | |
| 0.15.0 | 16 / 4 | |
| 0.14.1 | 16 / 4 | |
| 0.14.0 | 16 / 4 | |
| 0.13.1 | 16 / 4 | |
| 0.13.0 | 16 / 4 | |
| 0.12.4 | 16 / 4 | |
| 0.12.3 | 16 / 4 | |
| 0.12.2 | 16 / 4 | |
| 0.12.1 | 16 / 4 | |
| 0.12.0 | 15 / 5 | |
| 0.11.1 | 13 / 3 | |
| 0.11.0 | 13 / 3 | |
| 0.10.0 | 13 / 3 | |
| 0.9.0 | 14 / 2 |
v3.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.1.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.1.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2021-01-09, but blink1073 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.
v3.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2021-01-08, but blink1073 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.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2020-12-24, but jasongrout 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.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (echarles) than the most recent previously approved version (blink1073) on 2021-03-19, but echarles 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.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marthacryan) than the most recent previously approved version (blink1073) on 2020-10-23, but marthacryan 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.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2020-08-17, but blink1073 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.
v2.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2020-08-07, but blink1073 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.
v2.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2020-07-27, but jasongrout 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.
v2.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saulshanabrook) than the most recent previously approved version (blink1073) on 2020-07-15, but saulshanabrook 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.
v2.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saulshanabrook) than the most recent previously approved version (blink1073) on 2020-05-04, but saulshanabrook 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.
v2.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saulshanabrook) than the most recent previously approved version (blink1073) on 2020-04-06, but saulshanabrook 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.
v2.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saulshanabrook) than the most recent previously approved version (blink1073) on 2020-04-06, but saulshanabrook 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.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2020-02-28, but blink1073 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.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (saulshanabrook) on 2020-04-09, but blink1073 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.
v1.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2020-03-29, but blink1073 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.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2019-09-18, but jasongrout 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.
v1.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2019-09-10, but jasongrout 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.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2019-08-28, but jasongrout 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.
v1.0.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2019-08-21, but blink1073 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.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2019-08-09, but jasongrout 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.
v1.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2019-07-25, but jasongrout 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.
v1.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2019-07-09, but blink1073 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.
v1.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (darian) than the most recent previously approved version (blink1073) on 2019-06-28, but darian 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.
v0.19.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (blink1073) on 2018-10-05, but jasongrout 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.
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2018-08-18, but blink1073 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.
v0.18.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2018-08-16, but blink1073 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.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blink1073) than the most recent previously approved version (jasongrout) on 2018-07-25, but blink1073 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.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (darian) on 2018-04-14, but jasongrout 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.
v0.16.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jasongrout) than the most recent previously approved version (darian) on 2018-04-14, but jasongrout 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.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.