← Home

@steedos/metadata-registrar

- 此包是vscode扩展包`Steedos Extension Pack`元数据同步主要逻辑。

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

steedos-zhuangjianguosteedos-baozhoutaochenzhipeiyinlianghuisteedos-sunhaolin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): eval() used only to parse regex literals from strings starting with '/'; bounded input, not attacker-controlled. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads user-specified config file paths; expected behavior for a metadata registrar. ai
phantom-deps phantom-dep:ini AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:eval AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:glob AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:ioredis AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:archiver AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:compressing AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:dotenv-flow AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@steedos/client AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic false positive. ai

Versions (showing 21 of 21)

Version Deps Published
3.0.12 16 / 3
3.0.11 16 / 3
3.0.10 16 / 3
3.0.9 16 / 3
3.0.8 16 / 3
3.0.7 16 / 3
3.0.6 16 / 3
3.0.4 16 / 3
3.0.3 16 / 3
3.0.2 16 / 3
3.0.1 16 / 3
3.0.0 16 / 3
2.7.32 16 / 3
2.7.31 16 / 3
2.7.30 16 / 3
2.7.29 16 / 3
2.7.28 16 / 3
2.7.27 16 / 3
2.7.25 16 / 3
2.7.24 16 / 3
2.7.23 16 / 3

v3.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.7.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.