@podlite/editor-react
Rich text editor React component for Podlite — syntax highlighting, live preview, CodeMirror 6
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:lib/index.cjs | AI (source-diff): Bundled esbuild output, not obfuscation. | ai | |
| source-diff | net-exec-file:lib/index.cjs | AI (source-diff): Bundled deps (ajv codegen) trigger pattern, no real net+exec malware. | ai | |
| source-diff | net-exec-file:lib/index.esm.js | AI (source-diff): Same bundled build artifact as cjs counterpart. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function used in bundled ajv-style schema validator, standard pattern. | ai | |
| phantom-deps | phantom-dep:pod6 | AI (phantom-deps): pod6 is sibling @podlite package, plausibly used in build/types not caught by import scan. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-standing legitimate package with sparse metadata, not spam. | ai | |
| source-diff | obfuscated-file-transition:esm/index.js | AI (source-diff): esbuild bundle output from new build scripts, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file-transition:lib/index.js | AI (source-diff): esbuild bundle output from new build scripts, not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 45 versions; no provenance is common and not a risk signal here. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.0.59 | 13 / 0 | |
| 0.0.58 | 13 / 0 | |
| 0.0.57 | 10 / 0 | |
| 0.0.56 | 10 / 0 | |
| 0.0.55 | 10 / 0 | |
| 0.0.54 | 10 / 0 | |
| 0.0.53 | 10 / 0 | |
| 0.0.52 | 10 / 0 | |
| 0.0.51 | 10 / 0 | |
| 0.0.50 | 10 / 0 | |
| 0.0.49 | 10 / 0 | |
| 0.0.48 | 10 / 0 | |
| 0.0.47 | 10 / 0 | |
| 0.0.46 | 10 / 0 | |
| 0.0.45 | 10 / 0 | |
| 0.0.44 | 10 / 0 | |
| 0.0.43 | 10 / 0 | |
| 0.0.42 | 10 / 0 | |
| 0.0.41 | 9 / 0 | |
| 0.0.40 | 9 / 0 | |
| 0.0.39 | 8 / 0 | |
| 0.0.38 | 8 / 0 | |
| 0.0.37 | 8 / 0 | |
| 0.0.36 | 8 / 0 | |
| 0.0.35 | 8 / 0 | |
| 0.0.34 | 8 / 0 | |
| 0.0.33 | 8 / 0 | |
| 0.0.32 | 8 / 0 | |
| 0.0.31 | 3 / 4 | |
| 0.0.30 | 3 / 4 | |
| 0.0.29 | 3 / 4 | |
| 0.0.28 | 3 / 4 | |
| 0.0.27 | 3 / 4 | |
| 0.0.26 | 3 / 4 | |
| 0.0.25 | 3 / 4 | |
| 0.0.24 | 3 / 4 | |
| 0.0.23 | 3 / 4 | |
| 0.0.22 | 3 / 4 | |
| 0.0.21 | 3 / 4 | |
| 0.0.20 | 3 / 4 | |
| 0.0.19 | 3 / 4 | |
| 0.0.15 | 3 / 3 | |
| 0.0.14 | 3 / 9 | |
| 0.0.13 | 3 / 9 | |
| 0.0.12 | 3 / 9 | |
| 0.0.11 | 3 / 9 | |
| 0.0.10 | 3 / 9 | |
| 0.0.9 | 4 / 8 | |
| 0.0.8 | 4 / 8 | |
| 0.0.7 | 4 / 8 | |
| 0.0.6 | 4 / 8 | |
| 0.0.5 | 4 / 8 | |
| 0.0.4 | 4 / 8 | |
| 0.0.3 | 5 / 8 | |
| 0.0.2 | 5 / 7 | |
| 0.0.1 | 5 / 7 |
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.