@lumino/virtualdom
Lumino Virtual DOM
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:types-3.4/index.d.ts | AI (source-diff): TypeScript declaration file with long union type literals (HTML attribute names). Not obfuscated — this is standard .d.ts formatting for large union types generated by downlevel-dts. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by addition of types/ and types-3.4/ declaration directories, explicitly listed in package.json files array. Legitimate build artifact addition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Darian is already listed as a contributor in package.json; this is a legitimate team member addition in the JupyterLab/lumino project. | ai | |
| source-diff | obfuscated-file:types/index.d.ts | AI (source-diff): Long lines in types/index.d.ts are TypeScript union type declarations listing HTML attribute names — a legitimate pattern in .d.ts files, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher; lack of Sigstore attestation is a process gap, not a security risk for this package. | ai | |
| provenance | missing-githead | AI (provenance): Trusted JupyterLab ecosystem publisher (blink1073) with strong track record; missing gitHead reflects a CI/CD environment change, not a supply chain concern. | ai | |
| provenance | publisher-changed | AI (provenance): jupyterlab-release-bot is the official JupyterLab automation account with 3583 approved packages; transition from individual maintainer to release bot is expected and legitimate for this project. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 1 / 18 | |
| 2.0.3 | 1 / 18 | |
| 2.0.2 | 1 / 18 | |
| 2.0.1 | 1 / 23 | |
| 2.0.0 | 1 / 24 | |
| 1.14.3 | 1 / 22 | |
| 1.14.2 | 1 / 22 | |
| 1.14.1 | 1 / 22 | |
| 1.14.0 | 1 / 22 | |
| 1.13.0 | 1 / 22 | |
| 1.12.0 | 1 / 22 | |
| 1.11.2 | 1 / 22 | |
| 1.11.1 | 1 / 22 | |
| 1.11.0 | 1 / 22 | |
| 1.10.0 | 1 / 22 | |
| 1.9.0 | 1 / 22 | |
| 1.8.1 | 1 / 22 | |
| 1.8.0 | 1 / 22 | |
| 1.7.3 | 1 / 22 | |
| 1.7.2 | 1 / 22 | |
| 1.7.1 | 1 / 23 | |
| 1.7.0 | 1 / 22 | |
| 1.6.1 | 1 / 16 | |
| 1.6.0 | 1 / 16 | |
| 1.5.0 | 1 / 16 | |
| 1.4.1 | 1 / 16 | |
| 1.4.0 | 1 / 16 | |
| 1.3.0 | 1 / 16 | |
| 1.2.1 | 1 / 15 | |
| 1.2.0 | 1 / 14 |
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-03-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fcollonval.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.14.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jasongrout.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v1.14.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.
v1.13.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.
v1.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.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.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.