@mescius/wijmo.grid.grouppanel
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-org sibling package; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid | AI (dependencies): Same-org sibling package; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.input | AI (dependencies): Same-org sibling package; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid.filter | AI (dependencies): Same-org sibling package; stable pattern across all Wijmo releases. | ai | |
| phantom-deps | phantom-dep:@mescius/wijmo.input | AI (phantom-deps): Same-org declared dependency; false positive for this modular package structure. | ai | |
| provenance | no-provenance | AI (provenance): Commercial publisher; no provenance is consistent across all Wijmo versions. | ai | |
| license | uncommon-license:Commercial | AI (license): MESCIUS Wijmo is a known commercial product; Commercial license is expected. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.20261.52 | 4 / 0 | |
| 5.20261.50 | 4 / 0 | |
| 5.20261.48 | 4 / 0 | |
| 5.20252.44 | 4 / 0 | |
| 5.20252.42 | 4 / 0 | |
| 5.20251.40 | 4 / 0 | |
| 5.20251.34 | 4 / 0 | |
| 5.20242.30 | 4 / 0 | |
| 5.20242.21 | 4 / 0 | |
| 5.20241.19 | 4 / 0 |
v5.20261.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20251.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20241.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.