← Home

@adguard/dnr-rulesets

Utility to create AdGuard DNR rulesets for mv3 extensions

100
Versions
GPL-3.0-only
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ameshkovmaximtopblakhard

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 9479)

Version Deps Published
4.1.20260405200043 10 / 29
4.1.20260405190051 10 / 29
4.1.20260405180054 10 / 29
4.1.20260405170057 10 / 29
4.1.20260405160048 10 / 29
4.1.20260405150102 10 / 29
4.1.20260405140051 10 / 29
4.1.20260405130056 10 / 29
4.1.20260405120106 10 / 29
4.1.20260405110050 10 / 29
4.1.20260405100052 10 / 29
4.1.20260405090044 10 / 29
4.1.20260405080052 10 / 29
4.1.20260405070039 10 / 29
4.1.20260405060048 10 / 29
4.1.20260405050057 10 / 29
4.1.20260405040052 10 / 29
4.1.20260405030054 10 / 29
4.1.20260405020051 10 / 29
4.1.20260405010057 10 / 29
4.1.20260404230048 10 / 29
4.1.20260404220052 10 / 29
4.1.20260404210054 10 / 29
4.1.20260404200051 10 / 29
4.1.20260404190055 10 / 29
4.1.20260404180048 10 / 29
4.1.20260404170104 10 / 29
4.1.20260404160052 10 / 29
4.1.20260404150054 10 / 29
4.1.20260404140044 10 / 29
4.1.20260404120051 10 / 29
4.1.20260404100051 10 / 29
4.1.20260404090050 10 / 29
4.1.20260404080048 10 / 29
4.1.20260404070056 10 / 29
4.1.20260404060122 10 / 29
4.1.20260404050049 10 / 29
4.1.20260404040053 10 / 29
4.1.20260404030051 10 / 29
4.1.20260404020047 10 / 29
4.1.20260404010053 10 / 29
4.1.20260404000059 10 / 29
4.1.20260403230051 10 / 29
4.1.20260403220104 10 / 29
4.1.20260403210058 10 / 29
4.1.20260403200054 10 / 29
4.1.20260403190047 10 / 29
4.1.20260403180046 10 / 29
4.1.20260403170050 10 / 29
4.1.20260403150110 10 / 29
4.1.20260403140053 10 / 29
4.1.20260403130122 10 / 29
4.1.20260403120100 10 / 29
4.1.20260403110056 10 / 29
4.1.20260403100051 10 / 29
4.1.20260403090052 10 / 29
4.1.20260403070305 10 / 29
4.1.20260403060124 10 / 29
4.1.20260403040051 10 / 29
4.1.20260403030127 10 / 29
4.1.20260403010101 10 / 29
4.1.20260403000116 10 / 29
4.1.20260402220049 10 / 29
4.1.20260402210055 10 / 29
4.1.20260402190047 10 / 29
4.1.20260402160053 10 / 29
4.1.20260402150053 10 / 29
4.1.20260402140111 10 / 29
4.1.20260402130115 10 / 29
4.1.20260402120059 10 / 29
4.1.20260402110143 10 / 29
4.1.20260402100051 10 / 29
4.1.20260402090101 10 / 29
4.1.20260402080103 10 / 29
4.1.20260402070056 10 / 29
4.1.20260402060130 10 / 29
4.1.20260402050121 10 / 29
4.1.20260402040055 10 / 29
4.1.20260402030058 10 / 29
4.1.20260402020048 10 / 29
4.1.20260402010059 10 / 29
4.1.20260402000117 10 / 29
4.1.20260401230043 10 / 29
4.1.20260401220049 10 / 29
4.1.20260401210102 10 / 29
4.1.20260401200052 10 / 29
4.1.20260401180053 10 / 29
4.1.20260401170102 10 / 29
4.1.20260401160053 10 / 29
4.1.20260401150102 10 / 29
4.1.20260401140053 10 / 29
4.1.20260401130058 10 / 29
4.1.20260401120122 10 / 29
4.1.20260401110057 10 / 29
4.1.20260401100106 10 / 29
4.1.20260401090055 10 / 29
4.1.20260401070110 10 / 29
4.1.20260401060055 10 / 29
4.1.20260401050134 10 / 29
4.1.20260401040050 10 / 29
Showing 100 of 9479 Next page →
LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

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.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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