@spaceflow/publish
Spaceflow CI 发布插件,用于在发布流程中锁定/解锁分支
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): CI/CD publish automation is expected for a release tooling package; rapid publishes are normal for this workflow. | ai | |
| phantom-deps | phantom-dep:release-it-gitea | AI (phantom-deps): Config-file-only reference is expected for a release-it plugin; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@release-it/conventional-changelog | AI (phantom-deps): Config-file-only reference is expected for a release-it plugin; not a real phantom dep. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 5.0.11 | 3 / 2 | |
| 5.0.10 | 3 / 2 | |
| 5.0.9 | 3 / 2 | |
| 5.0.8 | 3 / 2 | |
| 5.0.7 | 3 / 2 | |
| 5.0.6 | 3 / 2 | |
| 5.0.5 | 3 / 2 | |
| 5.0.4 | 3 / 2 | |
| 5.0.3 | 3 / 2 | |
| 5.0.2 | 3 / 2 | |
| 5.0.1 | 3 / 2 | |
| 5.0.0 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.56.0 | 3 / 2 | |
| 0.55.0 | 3 / 2 | |
| 0.54.0 | 3 / 2 | |
| 0.53.0 | 3 / 2 | |
| 0.52.0 | 3 / 2 | |
| 0.51.0 | 3 / 2 | |
| 0.50.0 | 3 / 2 | |
| 0.49.0 | 3 / 2 | |
| 0.48.0 | 3 / 2 | |
| 0.47.0 | 3 / 2 | |
| 0.46.0 | 3 / 2 | |
| 0.45.0 | 3 / 2 | |
| 0.44.0 | 3 / 2 | |
| 0.43.0 | 3 / 2 | |
| 0.42.0 | 3 / 2 | |
| 0.41.0 | 3 / 2 | |
| 0.40.0 | 3 / 2 | |
| 0.39.0 | 3 / 2 | |
| 0.38.0 | 3 / 2 | |
| 0.37.0 | 3 / 2 | |
| 0.36.0 | 3 / 2 | |
| 0.35.0 | 3 / 2 | |
| 0.34.0 | 3 / 2 | |
| 0.33.0 | 3 / 2 | |
| 0.32.0 | 3 / 2 | |
| 0.31.0 | 3 / 2 | |
| 0.30.0 | 3 / 2 | |
| 0.29.0 | 3 / 2 | |
| 0.28.0 | 3 / 2 | |
| 0.27.0 | 3 / 2 | |
| 0.26.0 | 3 / 2 | |
| 0.25.0 | 3 / 2 | |
| 0.24.0 | 3 / 2 | |
| 0.23.0 | 3 / 2 | |
| 0.22.0 | 3 / 2 | |
| 0.21.3 | 3 / 2 | |
| 0.21.2 | 3 / 2 | |
| 0.21.1 | 3 / 2 |
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
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.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.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. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.