@spaceflow/core
Spaceflow 核心能力库
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:release-it-gitea | AI (dependencies): Phantom dep used only in release tooling config, not imported at runtime. | ai | |
| dependencies | unvetted-dep:@release-it/conventional-changelog | AI (dependencies): Phantom dep used only in release tooling config, not imported at runtime. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used to bypass bundler transformation for dynamic import of local file URLs; not user-controlled input. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding GitHub API file content response (base64 is the API's encoding); standard and benign. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @spaceflow/core; not impersonating 'cors'. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@rspack/cli | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:release-it-gitea | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@release-it/conventional-changelog | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:release-it | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env to add FORCE_COLOR is a standard CLI child-process pattern, not exfiltration. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 5.2.5 | 23 / 15 | |
| 5.2.4 | 23 / 15 | |
| 5.2.3 | 23 / 15 | |
| 5.2.2 | 23 / 15 | |
| 5.2.1 | 23 / 15 | |
| 5.2.0 | 23 / 15 | |
| 5.1.0 | 23 / 15 | |
| 5.0.1 | 23 / 15 | |
| 5.0.0 | 24 / 15 | |
| 0.31.0 | 24 / 15 | |
| 0.30.0 | 24 / 15 | |
| 0.29.0 | 24 / 15 | |
| 0.28.0 | 24 / 15 | |
| 0.27.0 | 24 / 15 | |
| 0.26.0 | 24 / 15 | |
| 0.25.0 | 24 / 15 | |
| 0.24.0 | 24 / 15 | |
| 0.23.0 | 24 / 15 | |
| 0.22.0 | 24 / 15 | |
| 0.21.0 | 24 / 15 | |
| 0.20.0 | 24 / 15 | |
| 0.19.0 | 24 / 15 | |
| 0.18.0 | 24 / 15 | |
| 0.17.0 | 24 / 15 | |
| 0.16.0 | 24 / 15 | |
| 0.15.0 | 24 / 15 | |
| 0.14.0 | 24 / 15 | |
| 0.13.0 | 24 / 15 | |
| 0.12.0 | 24 / 15 | |
| 0.11.0 | 24 / 15 | |
| 0.10.0 | 24 / 15 | |
| 0.9.0 | 24 / 15 | |
| 0.8.0 | 21 / 16 | |
| 0.7.0 | 22 / 15 | |
| 0.6.0 | 22 / 15 | |
| 0.5.0 | 22 / 15 | |
| 0.4.0 | 22 / 15 | |
| 0.3.0 | 22 / 15 | |
| 0.2.0 | 22 / 15 |
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.