← Home

@mescius/wijmo.barcode.specialized

10
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mescius

Keywords

controlcomponentuicontrol librarycomponent libraryui librarycontrol-librarycomponent-libraryui-librarygriddata griddata-griddatagridangular gridreact gridvue gridangular-gridreact-gridvue-grid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): MESCIUS does not publish with Sigstore provenance; stable pattern across all their packages. ai
license uncommon-license:Commercial AI (license): Wijmo is a known commercial library; Commercial license is expected and stable for this package. ai

Versions (showing 10 of 10)

Version Deps Published
5.20261.52 2 / 0
5.20261.50 2 / 0
5.20261.48 2 / 0
5.20252.44 2 / 0
5.20252.42 2 / 0
5.20251.40 2 / 0
5.20251.34 2 / 0
5.20242.30 2 / 0
5.20242.21 2 / 0
5.20241.19 2 / 0

v5.20261.52

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.20251.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.20242.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.20242.21

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.