@steedos/service-metadata-apps
- 用于管理应用元数据与缓存服务通信
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this package family; not a malware signal. | ai | |
| dependencies | unvetted-dep:moleculer | AI (dependencies): moleculer is a legitimate microservices framework; stable dependency across steedos packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo service package; sparse metadata is consistent across all @steedos/* packages. | ai | |
| phantom-deps | phantom-dep:moleculer-web | AI (phantom-deps): moleculer-web is a declared runtime dep used via config; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:ioredis | AI (phantom-deps): ioredis is a declared runtime dep used via config/indirect import in a moleculer service; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:moleculer | AI (phantom-deps): moleculer referenced in config/scripts; phantom-dep heuristic fires on config-only usage, stable false positive for this service package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 7 / 1 | |
| 3.0.13 | 7 / 1 | |
| 3.0.12 | 7 / 1 | |
| 3.0.11 | 7 / 1 | |
| 3.0.10 | 7 / 1 | |
| 3.0.9 | 7 / 1 | |
| 3.0.8 | 7 / 1 | |
| 3.0.7 | 7 / 1 | |
| 3.0.6 | 7 / 1 | |
| 3.0.4 | 7 / 1 | |
| 3.0.3 | 7 / 1 | |
| 3.0.2 | 7 / 1 | |
| 3.0.1 | 7 / 1 | |
| 3.0.0 | 7 / 1 | |
| 2.7.32 | 7 / 1 | |
| 2.7.31 | 7 / 1 | |
| 2.7.30 | 7 / 1 | |
| 2.7.29 | 7 / 1 | |
| 2.7.28 | 7 / 1 | |
| 2.7.27 | 7 / 1 | |
| 2.7.25 | 7 / 1 | |
| 2.7.24 | 7 / 1 | |
| 2.7.23 | 7 / 1 |
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.