xss-filters
Secure XSS Filters - Just sufficient output filtering to prevent XSS!
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/xss-filters.min-browserified.js | AI (source-diff): This is a standard browserified/minified browser distribution bundle for the xss-filters library. The content is clearly legitimate XSS-filtering logic with a Yahoo copyright header, not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change (adon → neraliu) occurred in 2015 within the Yahoo org; neraliu has a clean track record and the repo URL consistently points to github.com/yahoo/xss-filters. Legitimate maintainer transition. | ai | |
| license | uncommon-license:BSD | AI (license): BSD is a well-known permissive license; the license URL points to the official Yahoo/xss-filters repo. No legal risk. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.2.7 | 0 / 20 | |
| 1.2.6 | 0 / 10 | |
| 1.2.5 | 0 / 11 | |
| 1.2.4 | 0 / 10 | |
| 1.2.3 | 0 / 10 | |
| 1.2.2 | 0 / 10 | |
| 1.2.0 | 0 / 10 | |
| 1.1.2 | 0 / 10 | |
| 1.1.1 | 0 / 10 | |
| 1.1.0 | 0 / 10 | |
| 1.0.7 | 0 / 10 | |
| 1.0.6 | 0 / 10 | |
| 1.0.5 | 0 / 10 | |
| 1.0.4 | 0 / 10 | |
| 1.0.3 | 0 / 10 | |
| 1.0.2 | 0 / 11 | |
| 1.0.1 | 0 / 11 | |
| 1.0.0 | 0 / 11 |
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
3 findingsThis version was published by a different npm account than previous versions on 2015-07-10. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsThis version was published by a different npm account than previous versions on 2015-06-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2015-06-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.