bwip-js
JavaScript barcode generator supporting over 100 types and standards.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/bwip-js-gen.mjs | AI (source-diff): Generated minified barcode module with license banner; benign build output for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js-node.js | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js.js | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js-gen.mjs | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js-min.js | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js-rn.mjs | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js.mjs | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/bwip-js-node.mjs | AI (source-diff): Base64-encoded OpenType font data for barcode rendering; stable pattern for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.11.2 | 0 / 0 | |
| 4.11.1 | 0 / 0 | |
| 4.11.0 | 0 / 0 | |
| 4.10.2 | 0 / 0 | |
| 4.10.1 | 0 / 0 | |
| 4.10.0 | 0 / 0 | |
| 4.9.2 | 0 / 0 | |
| 4.9.1 | 0 / 0 | |
| 4.9.0 | 0 / 0 | |
| 4.8.0 | 0 / 0 | |
| 4.7.0 | 0 / 0 | |
| 4.6.0 | 0 / 0 | |
| 4.5.4 | 0 / 0 | |
| 4.5.3 | 0 / 0 | |
| 4.5.2 | 0 / 0 | |
| 4.5.1 | 0 / 0 | |
| 4.5.0 | 0 / 0 | |
| 4.4.0 | 0 / 0 | |
| 4.3.2 | 0 / 0 | |
| 4.3.1 | 0 / 0 | |
| 4.3.0 | 0 / 0 | |
| 4.2.0 | 0 / 0 | |
| 4.1.2 | 0 / 0 | |
| 4.1.1 | 0 / 0 | |
| 4.1.0 | 0 / 0 | |
| 4.0.1 | 0 / 0 | |
| 4.0.0 | 0 / 0 |
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.