← Home

@qualweb/wcag-techniques

13
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

joao-vicenteantonioestrigacarlosapaduartetellus

Keywords

wcaga11yaccessibilitywcag-2.1techniquesqualwebevaluation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/__webpack/wcag.bundle.js AI (source-diff): Webpack bundle output (lodash etc.), not true obfuscation. ai
source-diff net-exec-file:dist/__webpack/wcag.bundle.js AI (source-diff): Same webpack bundle; no concrete malicious network/exec behavior found. ai
publish-pattern dormant-publish AI (publish-pattern): Long-running legit package with consistent maintainer track record. ai

Versions (showing 13 of 13)

Version Deps Published
0.4.8 0 / 16
0.4.7 0 / 16
0.4.6 0 / 16
0.4.5 0 / 16
0.4.4 0 / 16
0.4.3 0 / 16
0.4.2 0 / 16
0.4.1 0 / 16
0.4.0 0 / 16
0.3.22 0 / 18
0.3.21 0 / 18
0.3.20 0 / 18
0.3.19 0 / 18

v0.4.8

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.

v0.4.2

3 findings
HIGH New obfuscated file: dist/__webpack/wcag.bundle.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 file with network + code execution: dist/__webpack/wcag.bundle.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.4.1

3 findings
HIGH New obfuscated file: dist/__webpack/wcag.bundle.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 file with network + code execution: dist/__webpack/wcag.bundle.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.4.0

3 findings
HIGH New obfuscated file: dist/__webpack/wcag.bundle.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 file with network + code execution: dist/__webpack/wcag.bundle.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.3.22

1 finding
LOW No provenance attestation provenance

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

v0.3.21

1 finding
LOW No provenance attestation provenance

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

v0.3.20

1 finding
LOW No provenance attestation provenance

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

v0.3.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.