← Home

@42ailab/42plugin

42plugin CLI - AI 插件管理工具

34
Versions
MIT
License
Yes
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

42ailab

Keywords

claudeclaude-codeplugincliai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@inquirer/prompts AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:cli-progress AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:proper-lockfile AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:pg AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:ora AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:tar AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:open AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:nanoid AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:commander AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:better-auth AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
phantom-deps phantom-dep:gray-matter AI (phantom-deps): Config-referenced dependency; stable pattern for this CLI package. ai
provenance no-provenance AI (provenance): No provenance is common; not a meaningful risk signal for this package. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall selects platform-specific prebuilt binary from optional deps; standard pattern for cross-platform CLI tools. ai

Versions (showing 34 of 34)

Version Deps Published
0.4.17 0 / 0
0.4.16 0 / 0
0.4.15 0 / 0
0.4.14 0 / 0
0.4.13 0 / 0
0.4.12 0 / 0
0.4.9 0 / 0
0.4.8 0 / 0
0.4.7 0 / 0
0.4.3 0 / 0
0.4.0 0 / 0
0.3.10 0 / 0
0.3.9 0 / 0
0.3.5 0 / 0
0.2.42 0 / 0
0.2.39 0 / 0
0.2.36 0 / 0
0.2.31 0 / 0
0.2.30 0 / 0
0.2.28 0 / 0
0.2.27 0 / 0
0.2.26 0 / 0
0.2.25 0 / 0
0.2.24 0 / 0
0.2.23 0 / 0
0.2.22 0 / 0
0.2.21 0 / 0
0.2.20 0 / 0
0.2.19 0 / 0
0.2.18 0 / 0
0.2.17 0 / 0
0.2.16 0 / 0
0.2.15 0 / 0
0.2.14 13 / 8

v0.4.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.42

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.39

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.36

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.16

1 finding
INFO No provenance attestation provenance

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

v0.2.15

1 finding
INFO No provenance attestation provenance

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

v0.2.14

1 finding
INFO No provenance attestation provenance

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