@adguard/scriptlets
AdGuard's JavaScript library of Scriptlets and Redirect resources
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): maximtop is an AdGuard team member with 3656 approved packages and 0 rejected — consistent with an internal org maintainer transition, not a compromise. | ai | |
| license | copyleft-license:GPL-3.0 | AI (license): AdGuard Scriptlets has always been GPL-3.0 licensed; this is the project's intended license, not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/trusted-types | AI (phantom-deps): @types/trusted-types is a TypeScript type definition used at compile time; declaring it as a runtime dep is a common pattern and poses no security risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established AdGuard package with 91 versions and clear GitHub repo; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 3 / 63 | |
| 2.4.2 | 3 / 63 | |
| 2.4.1 | 3 / 63 | |
| 2.3.1 | 3 / 63 | |
| 2.3.0 | 3 / 63 | |
| 2.2.16 | 3 / 63 | |
| 2.2.15 | 3 / 63 | |
| 2.2.14 | 3 / 63 | |
| 2.2.13 | 3 / 63 | |
| 2.2.12 | 3 / 63 | |
| 2.2.11 | 3 / 63 | |
| 2.2.10 | 3 / 63 | |
| 2.2.9 | 3 / 63 | |
| 2.2.8 | 3 / 63 | |
| 2.2.7 | 3 / 63 | |
| 2.2.6 | 3 / 63 | |
| 2.2.5 | 3 / 63 | |
| 2.2.4 | 3 / 63 | |
| 2.2.3 | 3 / 63 | |
| 2.2.2 | 3 / 63 | |
| 2.2.1 | 3 / 63 | |
| 2.2.0 | 2 / 64 | |
| 2.1.0 | 2 / 63 | |
| 2.0.1 | 3 / 63 |
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.