← Home

@juit/librebarcode

npm Repository Homepage

Encoders and fonts for EAN13 and Code128

83
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pfumagalli

Keywords

barcodefontsnodeean13eancode128encoder

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions publishing with SLSA attestation; this is the expected new publisher going forward. ai

Versions (showing 83 of 83)

Version Deps Published
2.0.84 0 / 8
2.0.83 0 / 8
2.0.82 0 / 8
2.0.81 0 / 8
2.0.80 0 / 8
2.0.79 0 / 8
2.0.78 0 / 8
2.0.77 0 / 8
2.0.76 0 / 8
2.0.75 0 / 8
2.0.74 0 / 8
2.0.73 0 / 8
2.0.72 0 / 8
2.0.71 0 / 8
2.0.70 0 / 8
2.0.69 0 / 8
2.0.68 0 / 8
2.0.67 0 / 8
2.0.66 0 / 8
2.0.65 0 / 8
2.0.64 0 / 8
2.0.63 0 / 8
2.0.62 0 / 8
2.0.61 0 / 8
2.0.60 0 / 8
2.0.59 0 / 8
2.0.58 0 / 8
2.0.57 0 / 8
2.0.56 0 / 8
2.0.54 0 / 8
2.0.53 0 / 8
2.0.52 0 / 8
2.0.51 0 / 8
2.0.50 0 / 8
2.0.49 0 / 8
2.0.48 0 / 8
2.0.47 0 / 8
2.0.46 0 / 8
2.0.45 0 / 8
2.0.44 0 / 8
2.0.43 0 / 8
2.0.42 0 / 8
2.0.41 0 / 8
2.0.40 0 / 8
2.0.39 0 / 8
2.0.38 0 / 8
2.0.37 0 / 8
2.0.36 0 / 8
2.0.35 0 / 8
2.0.34 0 / 8
2.0.33 0 / 8
2.0.32 0 / 8
2.0.31 0 / 8
2.0.30 0 / 8
2.0.29 0 / 8
2.0.28 0 / 8
2.0.27 0 / 8
2.0.26 0 / 8
2.0.25 0 / 8
2.0.24 0 / 8
2.0.23 0 / 8
2.0.21 0 / 8
2.0.20 0 / 8
2.0.19 0 / 8
2.0.18 0 / 8
2.0.17 0 / 8
2.0.16 0 / 8
2.0.15 0 / 8
2.0.14 0 / 8
2.0.13 0 / 8
2.0.12 0 / 8
2.0.11 0 / 8
2.0.10 0 / 8
2.0.9 0 / 8
2.0.8 0 / 8
2.0.7 0 / 8
2.0.6 0 / 8
2.0.5 0 / 8
2.0.4 0 / 8
2.0.3 0 / 8
2.0.2 0 / 8
2.0.1 0 / 8
2.0.0 0 / 8

v2.0.84

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.83

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.82

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.25

1 finding
LOW No provenance attestation provenance

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

v2.0.24

1 finding
LOW No provenance attestation provenance

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

v2.0.23

1 finding
LOW No provenance attestation provenance

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

v2.0.21

1 finding
LOW No provenance attestation provenance

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

v2.0.20

1 finding
LOW No provenance attestation provenance

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

v2.0.19

1 finding
LOW No provenance attestation provenance

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

v2.0.18

1 finding
LOW No provenance attestation provenance

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

v2.0.17

1 finding
LOW No provenance attestation provenance

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

v2.0.16

1 finding
LOW No provenance attestation provenance

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

v2.0.15

1 finding
LOW No provenance attestation provenance

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

v2.0.14

1 finding
LOW No provenance attestation provenance

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

v2.0.13

1 finding
LOW No provenance attestation provenance

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

v2.0.12

1 finding
LOW No provenance attestation provenance

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

v2.0.11

1 finding
LOW No provenance attestation provenance

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

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

1 finding
LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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