@steedos/service-api
- 系统api入口，如 graphql、元数据对象action。
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 | new-deps-added | AI (publish-pattern): New dep is the upstream moleculer-apollo-server replacing the steedos-vendored fork; benign de-vendoring. | ai | |
| dependencies | unvetted-dep:moleculer | AI (dependencies): moleculer is a well-known microservices framework; its use here is legitimate and stable across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-wide pattern; not indicative of malicious intent for @steedos packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across this package's history; low risk for established org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @steedos org package; sparse metadata is a pattern across their 1400+ versions, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared dependency used via config/schema files; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.0.13 | 12 / 1 | |
| 3.0.12 | 12 / 1 | |
| 3.0.11 | 12 / 1 | |
| 3.0.10 | 12 / 1 | |
| 3.0.9 | 12 / 1 | |
| 3.0.8 | 12 / 1 | |
| 3.0.7 | 12 / 1 | |
| 3.0.6 | 12 / 1 | |
| 3.0.4 | 12 / 1 | |
| 3.0.3 | 13 / 2 | |
| 3.0.2 | 13 / 2 | |
| 3.0.1 | 13 / 2 | |
| 3.0.0 | 13 / 2 | |
| 2.7.32 | 13 / 2 | |
| 2.7.31 | 13 / 2 | |
| 2.7.30 | 13 / 2 | |
| 2.7.29 | 13 / 2 | |
| 2.7.28 | 13 / 2 | |
| 2.7.27 | 13 / 2 | |
| 2.7.25 | 13 / 2 | |
| 2.7.24 | 13 / 2 | |
| 2.7.23 | 13 / 2 |
v3.0.13
2 findingsThis version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.