@blocklet/xss
blocklet prevent xss attack
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @blocklet/xss package; name reflects XSS sanitization purpose, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped @blocklet/xss package; name reflects XSS sanitization purpose, not a typosquat of rxjs. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.15.4 | 2 / 15 | |
| 0.3.16 | 2 / 15 | |
| 0.3.15 | 2 / 15 | |
| 0.3.14 | 2 / 15 | |
| 0.3.13 | 2 / 15 | |
| 0.3.12 | 2 / 15 | |
| 0.3.11 | 2 / 15 | |
| 0.3.10 | 2 / 15 | |
| 0.3.9 | 2 / 15 | |
| 0.3.8 | 2 / 15 | |
| 0.3.7 | 2 / 15 | |
| 0.3.6 | 2 / 15 | |
| 0.3.5 | 2 / 15 | |
| 0.3.4 | 2 / 15 | |
| 0.3.3 | 2 / 15 | |
| 0.3.2 | 2 / 15 | |
| 0.3.1 | 2 / 15 | |
| 0.3.0 | 2 / 15 | |
| 0.2.12 | 2 / 15 | |
| 0.2.11 | 2 / 15 | |
| 0.2.10 | 2 / 15 | |
| 0.2.9 | 2 / 15 | |
| 0.2.8 | 2 / 15 | |
| 0.2.7 | 2 / 15 | |
| 0.2.6 | 2 / 15 | |
| 0.2.5 | 2 / 15 | |
| 0.2.4 | 2 / 15 | |
| 0.2.3 | 2 / 15 | |
| 0.2.2 | 2 / 15 | |
| 0.2.1 | 2 / 15 | |
| 0.2.0 | 2 / 15 | |
| 0.1.36 | 2 / 15 | |
| 0.1.35 | 2 / 15 | |
| 0.1.34 | 2 / 15 | |
| 0.1.33 | 2 / 15 | |
| 0.1.32 | 2 / 15 | |
| 0.1.31 | 2 / 15 | |
| 0.1.30 | 2 / 15 | |
| 0.1.29 | 2 / 15 | |
| 0.1.28 | 2 / 15 | |
| 0.1.27 | 2 / 15 | |
| 0.1.26 | 2 / 15 | |
| 0.1.25 | 2 / 15 | |
| 0.1.24 | 2 / 15 | |
| 0.1.23 | 2 / 15 | |
| 0.1.22 | 2 / 15 | |
| 0.1.21 | 2 / 15 | |
| 0.1.20 | 2 / 15 | |
| 0.1.19 | 2 / 15 | |
| 0.1.18 | 2 / 15 | |
| 0.1.17 | 2 / 15 |
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.