← Home

@blocklet/meta

npm Homepage
24
Versions
—
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

wangshijungxw

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:cjk-length AI (dependencies): Small utility dep; consistent with package's text-validation purpose. ai
dependencies unvetted-dep:@ocap/asset AI (dependencies): First-party ArcBlock/OCAP scoped package, pinned monorepo version. ai
dependencies unvetted-dep:is-var-name AI (dependencies): Small utility dep; consistent with meta/validation package purpose. ai
dependencies unvetted-dep:@ocap/wallet AI (dependencies): First-party ArcBlock/OCAP scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@arcblock/jwt AI (dependencies): First-party ArcBlock scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@ocap/mcrypto AI (dependencies): First-party ArcBlock/OCAP scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@abtnode/db-cache AI (dependencies): First-party ArcBlock/abtnode scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@arcblock/did-ext AI (dependencies): First-party ArcBlock scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@arcblock/did-util AI (dependencies): First-party ArcBlock scoped package, pinned monorepo version. ai
dependencies unvetted-dep:@blocklet/constant AI (dependencies): First-party Blocklet scoped package, pinned monorepo version. ai
dependencies unvetted-dep:joi-extension-semver AI (dependencies): Standard Joi extension; consistent with validation package purpose. ai
dependencies unvetted-dep:@abtnode/docker-utils AI (dependencies): First-party ArcBlock/abtnode scoped package, pinned monorepo version. ai
phantom-deps phantom-dep:ajv AI (phantom-deps): Declared in package.json as runtime dep; heuristic false positive. ai
phantom-deps phantom-dep:@ocap/types AI (phantom-deps): Type-only usage common in TS packages; stable false positive. ai
phantom-deps phantom-dep:utility-types AI (phantom-deps): Type-only usage common in TS packages; stable false positive. ai
phantom-deps phantom-dep:@abtnode/db-cache AI (phantom-deps): First-party dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 24 of 24)

Version Deps Published
1.17.12 35 / 17
1.17.11 35 / 17
1.17.10 35 / 17
1.17.9 35 / 17
1.17.8 35 / 17
1.17.7 35 / 17
1.17.6 35 / 17
1.17.5 35 / 17
1.17.4 35 / 17
1.17.3 35 / 17
1.17.2 35 / 17
1.17.1 35 / 17
1.17.0 35 / 17
1.16.53 35 / 19
1.16.52 35 / 19
1.16.51 35 / 19
1.16.50 35 / 19
1.16.49 35 / 19
1.16.48 35 / 19
1.16.47 35 / 19
1.16.46 35 / 19
1.16.45 35 / 19
1.16.44 34 / 19
1.16.43 34 / 19

v1.17.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.

v1.17.11

1 finding
LOW No provenance attestation provenance

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

v1.17.10

1 finding
LOW No provenance attestation provenance

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

v1.17.9

1 finding
LOW No provenance attestation provenance

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

v1.17.8

1 finding
LOW No provenance attestation provenance

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

v1.17.7

1 finding
LOW No provenance attestation provenance

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

v1.17.6

1 finding
LOW No provenance attestation provenance

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

v1.17.5

1 finding
LOW No provenance attestation provenance

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

v1.17.4

1 finding
LOW No provenance attestation provenance

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

v1.17.3

1 finding
LOW No provenance attestation provenance

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

v1.17.2

1 finding
LOW No provenance attestation provenance

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

v1.17.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.

v1.17.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.

v1.16.53

1 finding
LOW No provenance attestation provenance

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

v1.16.52

1 finding
LOW No provenance attestation provenance

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

v1.16.51

1 finding
LOW No provenance attestation provenance

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

v1.16.50

1 finding
LOW No provenance attestation provenance

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

v1.16.49

1 finding
LOW No provenance attestation provenance

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

v1.16.48

1 finding
LOW No provenance attestation provenance

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

v1.16.47

1 finding
LOW No provenance attestation provenance

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

v1.16.46

1 finding
LOW No provenance attestation provenance

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

v1.16.45

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.

v1.16.44

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.

v1.16.43

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.