charset
Get the content charset from header and html content-type.
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
fengmk2
Keywords
charsetcontent-typeContentTypeContent-Typexmlencoding
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): File is the well-known google-code-prettify syntax highlighter auto-generated by Istanbul/lcov coverage tooling. Not a runtime file or malicious payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to accidentally published coverage/lcov-report/ directory (standard Istanbul output), not injected code. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 0 / 4 |
v1.0.1
2 findings
HIGH
New obfuscated file: coverage/lcov-report/prettify.js
source-diff
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.