@qualweb/best-practices
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Expected from switching to bundled webpack build output. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected from bundling dependencies via webpack. | ai | |
| source-diff | obfuscated-file:dist/__webpack/bp.bundle.js | AI (source-diff): Webpack bundle output (lodash etc.), not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/__webpack/bp.bundle.js | AI (source-diff): Bundled build artifact, pattern-matches on minified code not real dropper behavior. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.7.13 | 0 / 16 | |
| 0.7.12 | 0 / 16 | |
| 0.7.11 | 0 / 16 | |
| 0.7.10 | 0 / 16 | |
| 0.7.9 | 0 / 16 | |
| 0.7.8 | 0 / 16 | |
| 0.7.7 | 0 / 16 | |
| 0.7.6 | 0 / 16 | |
| 0.7.5 | 0 / 16 | |
| 0.7.4 | 0 / 16 | |
| 0.7.3 | 0 / 16 | |
| 0.7.2 | 0 / 16 | |
| 0.7.1 | 0 / 16 | |
| 0.7.0 | 0 / 16 | |
| 0.6.19 | 0 / 18 |
v0.7.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.