@archbase/core MIT 40 versions

@archbase/core

npm

Core utilities and foundation for Archbase React v3

40

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

edsonmartins

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): @archbase/core is a scoped React library, not a typo of cors; the name similarity is coincidental.	ai	2026/05/16
phantom-deps	phantom-dep:reflect-metadata	AI (phantom-deps): reflect-metadata is a known implicit runtime dep for inversify/class-transformer; not a real phantom dep.	ai	2026/05/16
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:react-use	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:usehooks-ts	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:class-validator	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:class-transformer	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16
phantom-deps	phantom-dep:@tanstack/react-query	AI (phantom-deps): Declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/16

Versions (showing 40 of 40)

Version	Deps	Published
4.0.28	23 / 11	2026-06-02
4.0.27	23 / 11	2026-05-29
4.0.26	23 / 11	2026-05-27
4.0.25	23 / 11	2026-05-27
4.0.24	23 / 11	2026-05-27
4.0.23	23 / 11	2026-05-27
4.0.22	23 / 11	2026-05-25
4.0.21	23 / 11	2026-05-25
4.0.20	23 / 11	2026-05-25
4.0.19	23 / 11	2026-05-21
4.0.18	23 / 11	2026-05-20
4.0.17	23 / 11	2026-05-19
4.0.4	23 / 11	2026-05-13
4.0.3	23 / 11	2026-05-13
4.0.2	23 / 11	2026-05-13
4.0.1	23 / 11	2026-05-05
4.0.0	23 / 11	2026-04-30
3.0.25	23 / 11	2026-04-17
3.0.23	23 / 11	2026-03-31
3.0.22	23 / 11	2026-03-27
3.0.21	23 / 11	2026-03-20
3.0.19	23 / 11	2026-03-20
3.0.18	23 / 11	2026-03-20
3.0.17	23 / 11	2026-03-18
3.0.16	23 / 11	2026-03-09
3.0.15	23 / 11	2026-03-08
3.0.14	23 / 11	2026-03-03
3.0.13	23 / 11	2026-02-23
3.0.12	23 / 11	2026-02-20
3.0.11	23 / 11	2026-02-19
3.0.10	23 / 11	2026-02-15
3.0.9	23 / 11	2026-02-14
3.0.8	23 / 11	2026-02-07
3.0.7	23 / 11	2026-02-04
3.0.6	23 / 11	2026-02-03
3.0.5	23 / 11	2026-02-02
3.0.4	23 / 11	2026-01-27
3.0.3	23 / 11	2026-01-26
3.0.2	23 / 11	2026-01-21
3.0.0	23 / 10	2026-01-14

v4.0.28

1 finding

LOW No provenance attestation provenance

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

v4.0.27

1 finding

LOW No provenance attestation provenance

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

v4.0.26

1 finding

LOW No provenance attestation provenance

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

v4.0.25

1 finding

LOW No provenance attestation provenance

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

v4.0.24

1 finding

LOW No provenance attestation provenance

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

v4.0.23

1 finding

LOW No provenance attestation provenance

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

v4.0.22

1 finding

LOW No provenance attestation provenance

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

v4.0.21

1 finding

LOW No provenance attestation provenance

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

v4.0.20

1 finding

LOW No provenance attestation provenance

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

v4.0.19

1 finding

LOW No provenance attestation provenance

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

v4.0.18

1 finding

LOW No provenance attestation provenance

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

v4.0.17

1 finding

LOW No provenance attestation provenance

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

v4.0.4

2 findings

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

Package name '@archbase/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.

v4.0.3

2 findings

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

Package name '@archbase/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.

v4.0.2

2 findings

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

Package name '@archbase/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.

v4.0.1

2 findings

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

Package name '@archbase/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.

v4.0.0

2 findings

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

Package name '@archbase/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.

v3.0.25

2 findings

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

Package name '@archbase/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.

v3.0.23

2 findings

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

Package name '@archbase/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.

v3.0.22

2 findings

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

Package name '@archbase/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.

v3.0.21

2 findings

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

Package name '@archbase/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.

v3.0.19

2 findings

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

Package name '@archbase/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.

v3.0.18

2 findings

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

Package name '@archbase/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.

v3.0.17

2 findings

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

Package name '@archbase/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.

v3.0.16

2 findings

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

Package name '@archbase/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.

v3.0.15

2 findings

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

Package name '@archbase/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.

v3.0.14

2 findings

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

Package name '@archbase/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.

v3.0.13

2 findings

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

Package name '@archbase/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.

v3.0.12

2 findings

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

Package name '@archbase/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.

v3.0.11

2 findings

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

Package name '@archbase/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.

v3.0.10

2 findings

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

Package name '@archbase/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.

v3.0.9

2 findings

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

Package name '@archbase/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.

v3.0.8

2 findings

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

Package name '@archbase/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.

v3.0.7

2 findings

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

Package name '@archbase/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.

v3.0.6

2 findings

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

Package name '@archbase/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.

v3.0.5

2 findings

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

Package name '@archbase/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.

v3.0.4

2 findings

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

Package name '@archbase/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.

v3.0.3

2 findings

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

Package name '@archbase/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.

v3.0.2

2 findings

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

Package name '@archbase/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.

v3.0.0

2 findings

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

Package name '@archbase/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.