@steedos/metadata-api
- 此包用于vscode扩展包`Steedos Extension Pack`元数据相关操作，如retrive、deploy等。
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes uploaded file buffer from base64 in a deploy router — standard file upload handling, not obfuscation. | ai | |
| phantom-deps | phantom-dep:dotenv-flow | AI (phantom-deps): dotenv-flow is declared as a dependency; phantom-dep heuristic false positive for config-only usage. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 12 / 1 | |
| 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 | |
| 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.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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
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. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.