← Home

@everymatrix/lottery-subscription

7
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

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releasemariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstrulea.sebastianstefan.vladgoe.sutadragos.bodeamaria.bumbarstefanaotong.woodtikarncatalinpoclidliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@widgets-monorepo/vaadin-facade AI (phantom-deps): Declared in package.json as a monorepo sibling dep; referenced in config files, stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo component; missing metadata is a consistent pattern across this package family, not a spam/malware signal. ai
npm-metadata no-description AI (npm-metadata): Consistent with internal monorepo component pattern across all versions. ai
provenance no-provenance AI (provenance): No provenance across all 287 versions; stable pattern for this publisher. ai

Versions (showing 7 of 7)

Version Deps Published
1.93.4 1 / 0
1.93.3 1 / 0
1.90.34 1 / 0
1.90.33 1 / 0
1.84.2 1 / 0
1.83.6 1 / 0
1.80.19 1 / 0

v1.90.34

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.

v1.90.33

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.

v1.84.2

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.

v1.83.6

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.

v1.80.19

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.