@aeria-ui/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

tartuffe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped monorepo package @aeria-ui/core; not a typosquat of cors — name similarity is coincidental.	ai	2026/05/02
install-scripts	install-script:postinstall	AI (install-scripts): Runs a local dist script with \|\| true fallback; consistent pattern across 101 versions of this monorepo package.	ai	2026/05/02
phantom-deps	phantom-dep:vue-demi	AI (phantom-deps): vue-demi is a declared runtime dependency used in config/build context; phantom-dep heuristic is a false positive here.	ai	2026/05/02

Versions (showing 5 of 5)

Version	Deps	Published
0.0.124	6 / 6	2026-04-29
0.0.123	6 / 6	2026-04-06
0.0.121	6 / 6	2026-02-26
0.0.117	6 / 6	2025-12-07
0.0.102	5 / 6	2025-05-22

v0.0.124

3 findings

HIGH Package has 'postinstall' script install-scripts

Script: node dist/__scripts__/postinstall.js || true

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

Package name '@aeria-ui/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.0.123

3 findings

HIGH Package has 'postinstall' script install-scripts

Script: node dist/__scripts__/postinstall.js || true

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

Package name '@aeria-ui/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.0.121

1 finding

LOW No provenance attestation provenance

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

v0.0.117

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

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.