← Home

qrcode-generator

npm Repository Homepage

QR Code Generator implementation in JavaScript.

24
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kazuhikoarase

Keywords

qrqrcodegenerator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Informational; long-standing package by original author without provenance attestation is not a security risk. ai
source-diff encoded-string-file:test/qrcode.js AI (source-diff): Base64-encoded GIF in test fixture is expected output for a QR code generator library; stable false positive. ai
source-diff obfuscated-file:qrcode_SJIS.js AI (source-diff): SJIS character encoding lookup table (base64-encoded Unicode-to-SJIS mapping) is expected for QR code SJIS support; not obfuscation. ai
source-diff obfuscated-file:qrcode_SJIS.mjs AI (source-diff): File is a SJIS character encoding lookup table for QR code generation, not obfuscated code. Long lines are base64-encoded byte mappings, expected for this package. ai
source-diff obfuscated-file:dist/qrcode_SJIS.mjs AI (source-diff): ESM variant of SJIS encoding table; same base64 data table, not obfuscation. ai
source-diff obfuscated-file:dist/qrcode_SJIS.js AI (source-diff): SJIS character encoding lookup table (base64 data) for QR code Japanese support; not obfuscated code. ai
source-diff obfuscated-file:experiment/vt/src/main/qrcode_SJIS.ts AI (source-diff): SJIS character encoding lookup table for QR code generation; long encoded lines are inherent to the data, not obfuscation. ai
source-diff encoded-string-file:test/qrcode-test-impl.js AI (source-diff): Base64-encoded GIF used as expected test output for QR code image generation; standard test fixture. ai

Versions (showing 24 of 24)

Version Deps Published
2.0.4 0 / 2
2.0.2 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2
1.5.2 0 / 1
1.5.1 0 / 2
1.5.0 0 / 2
1.4.4 0 / 1
1.4.3 0 / 1
1.4.2 0 / 1
1.4.1 0 / 1
1.4.0 0 / 0
1.3.1 0 / 0
1.3.0 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.7 0 / 0
1.0.6 0 / 0
1.0.5 0 / 0
1.0.4 0 / 0
1.0.3 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v2.0.4

3 findings
HIGH New obfuscated file: experiment/vt/src/main/qrcode_SJIS.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH Long encoded string in modified file: test/qrcode-test-impl.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

3 findings
HIGH New obfuscated file: dist/qrcode_SJIS.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/qrcode_SJIS.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.2

2 findings
HIGH New obfuscated file: qrcode_SJIS.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.1

3 findings
HIGH New obfuscated file: dist/qrcode_SJIS.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/qrcode_SJIS.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.0

2 findings
HIGH New obfuscated file: qrcode_SJIS.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.4.3

2 findings
HIGH Long encoded string in modified file: test/qrcode.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.4.2

2 findings
HIGH Long encoded string in modified file: test/qrcode.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
INFO No provenance attestation provenance

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

v1.3.0

1 finding
INFO No provenance attestation provenance

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

v1.2.0

1 finding
INFO No provenance attestation provenance

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

v1.1.0

1 finding
INFO No provenance attestation provenance

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

v1.0.7

1 finding
INFO No provenance attestation provenance

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

v1.0.6

1 finding
INFO No provenance attestation provenance

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

v1.0.5

1 finding
INFO No provenance attestation provenance

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

v1.0.4

1 finding
INFO No provenance attestation provenance

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

v1.0.3

1 finding
INFO No provenance attestation provenance

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

v1.0.2

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.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.