← Home

@wovin/core

15
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tennoxgotjoshua

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/chunk-CDYQMETJ.min.js AI (source-diff): Bundled chunk imports MobX, multiformats, crypto libs — standard build output, not malware. ai
bogus-package bogus-package AI (bogus-package): Established package with 97 versions and real download volume; missing metadata is a style choice, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this established package; not a malice signal. ai
phantom-deps phantom-dep:@libp2p/crypto AI (phantom-deps): Same bundled ESM pattern; stable false positive for this package. ai
phantom-deps phantom-dep:hash-wasm AI (phantom-deps): Platform-specific binary; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:@oddjs/odd AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:besonders-logger AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:safe-stable-stringify AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Declared in dependencies, likely used via re-exports or config; stable false positive for this package. ai
phantom-deps phantom-dep:iso-kv AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for bundled/re-exported usage. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @wovin/core is unrelated to cors; Levenshtein match is a false positive for this established package. ai

Versions (showing 15 of 15)

Version Deps Published
0.1.36 18 / 7
0.1.34 18 / 7
0.1.33 18 / 7
0.1.32 18 / 7
0.1.30 18 / 7
0.1.29 18 / 7
0.1.28 18 / 7
0.1.27 18 / 7
0.1.26 16 / 7
0.1.25 16 / 7
0.1.24 16 / 7
0.1.23 16 / 7
0.0.23 12 / 7
0.0.21 12 / 7
0.0.16 12 / 7

v0.1.36

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@wovin/core' is 1 edit(s) away from popular package 'cors'.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.34

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.33

2 findings
HIGH New file with network + code execution: dist/chunk-CDYQMETJ.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.32

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.30

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.29

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.28

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.27

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.24

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.1.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.0.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.

v0.0.21

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.

v0.0.16

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.