← Home

@revealui/core

13
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

revealui-org

Keywords

revealuicmsadmincollectionsrest-apiruntimerich-text

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; consistent with CI/CD automation for this org. ai
phantom-deps phantom-dep:sharp AI (phantom-deps): Sharp is a well-known native image processing library commonly declared as a runtime dependency but used implicitly; this is expected behavior for this package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @revealui/core is a scoped CMS framework package; the Levenshtein match to 'cors' is a false positive with no plausible confusion vector. ai
phantom-deps phantom-dep:@lexical/clipboard AI (phantom-deps): @lexical/clipboard is a legitimate Meta/Lexical package; phantom-dep flag is a minor packaging concern, not a security risk. ai

Versions (showing 13 of 13)

Version Deps Published
0.9.0 26 / 9
0.8.0 26 / 9
0.7.0 25 / 9
0.6.0 25 / 9
0.5.6 25 / 9
0.5.5 25 / 9
0.5.4 25 / 9
0.5.3 25 / 9
0.5.2 25 / 9
0.5.0 25 / 9
0.3.0 25 / 9
0.2.1 23 / 9
0.2.0 24 / 9

v0.9.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.8.0

2 findings
HIGH Publisher changed: revealui-org → GitHub Actions (on 2026-05-26) provenance

This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.

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

2 findings
HIGH Publisher changed: revealui-org → GitHub Actions (on 2026-05-16) provenance

This version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.

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

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

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

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

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

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.0

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

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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