← Home

@cabloy/compose

npm
12
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

zhennann

Keywords

cabloyframework

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): @cabloy/* is a large monorepo framework; mass-production, no-deps, tiny-payload signals are structural, not malicious. ai

Versions (showing 12 of 12)

Version Deps Published
2.1.5 0 / 0
2.1.4 0 / 0
2.1.3 0 / 2
2.1.2 0 / 2
2.1.1 0 / 2
2.0.15 0 / 0
2.0.14 0 / 0
2.0.13 0 / 0
2.0.12 0 / 0
2.0.10 0 / 0
2.0.7 0 / 2
2.0.6 0 / 2

v2.1.5

2 findings
HIGH Low-value / spam package indicators (5 signals, score 8) bogus-package

Matched 5 signal(s), weighted score 8: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 2989 bytes total.

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.1.4

2 findings
HIGH Low-value / spam package indicators (5 signals, score 8) bogus-package

Matched 5 signal(s), weighted score 8: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 2989 bytes total.

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.1.3

2 findings
HIGH Low-value / spam package indicators (4 signals, score 7) bogus-package

Matched 4 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 3108 bytes total.

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.1.2

2 findings
HIGH Low-value / spam package indicators (4 signals, score 7) bogus-package

Matched 4 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 3108 bytes total.

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.1.1

2 findings
HIGH Low-value / spam package indicators (4 signals, score 7) bogus-package

Matched 4 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 3108 bytes total.

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.0.15

2 findings
HIGH Low-value / spam package indicators (5 signals, score 8) bogus-package

Matched 5 signal(s), weighted score 8: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'zhennann' owns 250 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 2 code file(s), 2990 bytes total.

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.0.14

1 finding
LOW No provenance attestation provenance

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

v2.0.13

1 finding
LOW No provenance attestation provenance

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

v2.0.12

1 finding
LOW No provenance attestation provenance

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

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.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.