@adguard/tswebextension
This is a TypeScript library that implements AdGuard's extension API
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (3686 approved, 0 rejected); dormancy likely reflects release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:chrome-types | AI (dependencies): chrome-types is a well-known Google Chrome API type definitions package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@adguard/assistant | AI (dependencies): First-party AdGuard dependency from the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@adguard/extended-css | AI (dependencies): First-party AdGuard dependency from the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@adguard/text-encoding | AI (dependencies): First-party AdGuard dependency from the same org; stable false positive. | ai | |
| phantom-deps | phantom-dep:chrome-types | AI (phantom-deps): chrome-types is a type-only dev dependency referenced in tsconfig; not a runtime import. | ai | |
| phantom-deps | phantom-dep:superjson | AI (phantom-deps): superjson is a legitimate runtime dep used indirectly; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 20 / 42 | |
| 4.1.1 | 20 / 42 | |
| 4.0.6 | 20 / 40 | |
| 4.0.5 | 20 / 40 | |
| 4.0.4 | 20 / 40 | |
| 4.0.3 | 20 / 40 | |
| 4.0.2 | 20 / 40 | |
| 4.0.1 | 20 / 40 | |
| 4.0.0 | 20 / 40 | |
| 3.2.19 | 20 / 40 | |
| 3.2.18 | 20 / 40 | |
| 3.2.17 | 20 / 40 | |
| 3.2.16 | 20 / 40 | |
| 3.2.15 | 20 / 40 |
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.