@seafile/slate-react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:is-hotkey | AI (phantom-deps): Bundled dist build; dep used internally, not scannable as source import. | ai | |
| phantom-deps | phantom-dep:debounce | AI (phantom-deps): Bundled dist build; dep used internally, not scannable as source import. | ai | |
| phantom-deps | phantom-dep:direction | AI (phantom-deps): Bundled dist build; dep used internally, not scannable as source import. | ai | |
| phantom-deps | phantom-dep:scroll-into-view-if-needed | AI (phantom-deps): Bundled dist build; dep used internally, not scannable as source import. | ai | |
| phantom-deps | phantom-dep:is-window | AI (phantom-deps): Likely used in bundled source; benign utility dep, no install-time execution. | ai | |
| source-diff | net-exec-file:dist/slate-react.min.js | AI (source-diff): Minified bundle of same source, same false-positive pattern. | ai | |
| source-diff | obfuscated-file:dist/slate-react.js | AI (source-diff): Rollup/UMD bundle output, not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/slate-react.js | AI (source-diff): Bundled build file; no actual network+exec dropper behavior observed. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Bundled dist files added; expected growth from build output, not injected payload. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Framework-scoped type package; loaded by convention in React libraries. | ai | |
| phantom-deps | phantom-dep:is-plain-object | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/is-hotkey | AI (phantom-deps): Framework-scoped type package; loaded by convention in React libraries. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.92.8 | 9 / 13 | |
| 0.92.7 | 9 / 13 | |
| 0.92.6 | 9 / 13 | |
| 0.92.5 | 9 / 13 | |
| 0.92.4 | 9 / 13 | |
| 0.92.3 | 9 / 13 | |
| 0.92.2 | 9 / 13 | |
| 0.92.1 | 9 / 13 | |
| 0.92.0 | 9 / 13 | |
| 0.54.13 | 9 / 2 | |
| 0.54.12 | 9 / 2 | |
| 0.54.11 | 9 / 2 | |
| 0.54.10 | 9 / 2 | |
| 0.54.9 | 9 / 2 | |
| 0.54.8 | 9 / 2 | |
| 0.54.7 | 9 / 2 | |
| 0.54.6 | 9 / 2 | |
| 0.54.5 | 9 / 2 | |
| 0.1.8 | 16 / 6 | |
| 0.1.7 | 16 / 6 | |
| 0.1.6 | 16 / 6 | |
| 0.1.4 | 14 / 5 | |
| 0.1.3 | 14 / 5 | |
| 0.1.2 | 14 / 5 | |
| 0.1.1 | 14 / 5 | |
| 0.1.0 | 14 / 5 |
v0.92.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.