@fe-free/core
React 业务核心组件库：CRUD、ProForm 扩展、布局、路由、树、上传等（Antd + ProComponents）
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ant-design/x-markdown | AI (dependencies): @ant-design/x-markdown is part of the official Ant Design ecosystem; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistently missing description across all versions; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal/private-style package with 255 versions; missing metadata is a stable characteristic, not a malware signal. | ai | |
| phantom-deps | phantom-dep:rehype-raw | AI (phantom-deps): Markdown-related peer/optional dep referenced in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Markdown-related dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Markdown-related dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:github-markdown-css | AI (phantom-deps): CSS dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-syntax-highlighter | AI (phantom-deps): Markdown/syntax dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@codemirror/lang-html | AI (phantom-deps): Config-referenced optional language plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-ace | AI (phantom-deps): Config-referenced peer; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@codemirror/lang-sql | AI (phantom-deps): Config-referenced peer; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@codemirror/lang-xml | AI (phantom-deps): Config-referenced peer; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Config-referenced peer; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @fe-free/core is a React UI library; name similarity to 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 51 of 143)
| Version | Deps | Published |
|---|---|---|
| 6.0.27 | 22 / 0 | |
| 6.0.26 | 22 / 0 | |
| 6.0.25 | 22 / 0 | |
| 6.0.24 | 22 / 0 | |
| 6.0.23 | 22 / 0 | |
| 6.0.22 | 22 / 0 | |
| 6.0.21 | 22 / 0 | |
| 6.0.20 | 22 / 0 | |
| 6.0.19 | 22 / 0 | |
| 6.0.18 | 22 / 0 | |
| 6.0.17 | 22 / 0 | |
| 6.0.16 | 22 / 0 | |
| 6.0.15 | 22 / 0 | |
| 6.0.14 | 22 / 0 | |
| 6.0.13 | 22 / 0 | |
| 6.0.12 | 22 / 0 | |
| 6.0.11 | 22 / 0 | |
| 6.0.10 | 22 / 0 | |
| 6.0.9 | 22 / 0 | |
| 6.0.8 | 22 / 0 | |
| 6.0.7 | 31 / 0 | |
| 6.0.6 | 31 / 0 | |
| 6.0.5 | 31 / 0 | |
| 6.0.4 | 31 / 0 | |
| 6.0.3 | 31 / 0 | |
| 6.0.2 | 31 / 0 | |
| 6.0.1 | 31 / 0 | |
| 5.0.0 | 29 / 0 | |
| 4.2.5 | 31 / 0 | |
| 4.2.4 | 31 / 0 | |
| 4.2.3 | 31 / 0 | |
| 4.2.2 | 31 / 0 | |
| 4.2.1 | 31 / 0 | |
| 4.2.0 | 31 / 0 | |
| 4.1.47 | 31 / 0 | |
| 4.1.46 | 31 / 0 | |
| 4.1.45 | 31 / 0 | |
| 4.1.44 | 31 / 0 | |
| 4.1.43 | 31 / 0 | |
| 4.1.42 | 31 / 0 | |
| 4.1.41 | 29 / 0 | |
| 4.1.40 | 29 / 0 | |
| 4.1.39 | 29 / 0 | |
| 4.1.38 | 29 / 0 | |
| 4.1.37 | 29 / 0 | |
| 4.1.36 | 29 / 0 | |
| 4.1.35 | 29 / 0 | |
| 4.1.34 | 29 / 0 | |
| 4.1.33 | 29 / 0 | |
| 4.1.32 | 29 / 0 | |
| 4.1.31 | 29 / 0 |
v6.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.25
2 findingsPackage name '@fe-free/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.24
2 findingsPackage name '@fe-free/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.