@adguard/dnr-rulesets
Utility to create AdGuard DNR rulesets for mv3 extensions
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/filters/local_script_rules.js | AI (source-diff): This file contains AdGuard scriptlet filter rules — minified JS strings mapped to expanded implementations. This is expected content for an ad-blocking DNR ruleset package, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/filters/chromium-mv3/local_script_rules.js | AI (source-diff): These files contain AdGuard's scriptlet lookup tables — minified ad-blocking JS used as object keys with expanded implementations as values. This is the package's documented design, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/filters/opera-mv3/local_script_rules.js | AI (source-diff): Same as chromium-mv3 variant: AdGuard scriptlet lookup tables with minified keys and readable implementations. Expected build artifact for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Package has 13,351 versions with timestamp-based version numbers, indicating a fully automated filter-list update pipeline. Rapid publishing is the normal operating mode for this package. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): CLI tool legitimately uses chokidar for file watching; declared in dependencies and referenced in config files. | ai | |
| dependencies | unvetted-dep:@adguard/agtree | AI (dependencies): First-party AdGuard dependency in the same org scope; expected internal dependency for this package. | ai | |
| phantom-deps | phantom-dep:@adguard/re2-wasm | AI (phantom-deps): First-party AdGuard dependency declared in package.json; phantom-dep flag is a false positive for same-org packages. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI tool legitimately uses commander for CLI argument parsing; declared in dependencies. | ai | |
| dependencies | unvetted-dep:@adguard/logger | AI (dependencies): First-party AdGuard dependency in the same org scope; expected internal dependency for this package. | ai | |
| dependencies | unvetted-dep:@adguard/re2-wasm | AI (dependencies): First-party AdGuard dependency in the same org scope; expected internal dependency for this package. | ai | |
| dependencies | unvetted-dep:@adguard/tsurlfilter | AI (dependencies): First-party AdGuard dependency in the same org scope; expected internal dependency for this package. | ai |
Versions (showing 51 of 8738)
v4.2.20260607050129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260607040102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260607030102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260607010109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260607000104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606230057
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606220057
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606210101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606200058
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606190101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606170054
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606160100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606140100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606130101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606110100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606080056
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606070046
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606060109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606040059
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606030058
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606020100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260606010103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605220057
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605210105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605200100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605180055
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605170058
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605160101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605150101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605140058
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605130100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605120055
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605110117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605100149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605090100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605060116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605040105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605030100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605020056
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605010105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260605000106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604220059
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604210055
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604190100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604180057
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604170101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604150137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604120100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604110103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604100102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20260604090111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.