@cp949/console-feed
A React component that displays console logs from the current page, an iframe or transported across a server
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/Component/theme/default.js | AI (source-diff): tsc-compiled dist output with embedded base64 image data, not true obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Expected dist growth from normal build, not injected code. | ai | |
| source-diff | obfuscated-file:dist/Component/index.js | AI (source-diff): Standard TS compiler helpers, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/Component/elements.js | AI (source-diff): Standard TS compiler helpers, not obfuscated. | ai | |
| provenance | missing-githead | AI (provenance): Publish environment metadata gap, no behavioral risk; publisher has clean track record. | ai | |
| source-diff | net-exec-file:dist/index.mjs | AI (source-diff): Bundled component code with linkify/DOMPurify imports; no malicious network+exec behavior. | ai | |
| source-diff | net-exec-file:dist/Hook/index.mjs | AI (source-diff): Bundled tsup output; sample shows benign console-hook logic, no fetched/executed payload. | ai | |
| dependencies | unvetted-dep:react-inline-center | AI (dependencies): Small pinned UI helper dep, consistent across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): dompurify replaces isomorphic-dompurify wrapper; legitimate refactor. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 4 / 9 | |
| 3.7.0 | 4 / 9 | |
| 3.6.8 | 8 / 9 | |
| 3.6.7 | 8 / 8 | |
| 3.6.6 | 8 / 8 | |
| 3.6.5 | 8 / 11 | |
| 3.6.3 | 8 / 11 | |
| 3.6.2 | 8 / 11 | |
| 3.6.1 | 8 / 13 | |
| 3.6.0 | 8 / 15 |
v3.7.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
10 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cp949.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
v3.6.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cp949.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cp949.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.