@vertz/core — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

viniciusdacal

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	slsa-provenance	AI (provenance): Package consistently published with SLSA provenance attestation; strong supply chain integrity signal.	ai	2026/05/09
typosquat	typosquat.levenshtein:cors	AI (typosquat): @vertz/core is a scoped framework package, not a typosquat of cors; the name similarity is coincidental.	ai	2026/05/09

Versions (showing 20 of 20)

Version	Deps	Published
0.2.80	1 / 0	2026-05-02
0.2.78	1 / 0	2026-04-22
0.2.76	1 / 0	2026-04-20
0.2.75	1 / 0	2026-04-19
0.2.74	1 / 0	2026-04-19
0.2.73	1 / 0	2026-04-19
0.2.71	1 / 0	2026-04-17
0.2.70	1 / 0	2026-04-17
0.2.68	1 / 0	2026-04-17
0.2.67	1 / 0	2026-04-16
0.2.66	1 / 0	2026-04-16
0.2.64	1 / 0	2026-04-14
0.2.63	1 / 0	2026-04-14
0.2.62	1 / 0	2026-04-14
0.2.61	1 / 0	2026-04-14
0.2.60	1 / 0	2026-04-13
0.2.59	1 / 0	2026-04-12
0.2.55	1 / 0	2026-04-09
0.1.0	1 / 4	2026-02-08
0.0.2	1 / 4	2026-02-08

v0.2.80

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

2 findings

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

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

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

1 finding

INFO Has SLSA provenance attestation provenance

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

v0.0.2

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.