← Home

@expo/styleguide-cookie-consent

npm Repository Homepage

Cookie consent provider for Expo websites with c15t integration.

22
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

idebrentvatneevanbaconexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurman

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@c15t/react AI (phantom-deps): Dependency is referenced in config files per phantom-dep finding; consistent with a wrapper/integration package pattern. ai
phantom-deps phantom-dep:@c15t/scripts AI (phantom-deps): Dependency is referenced in config files per phantom-dep finding; consistent with a wrapper/integration package pattern. ai
phantom-deps phantom-dep:@radix-ui/react-slot AI (phantom-deps): Declared runtime dependency; used by Radix UI components. ai
phantom-deps phantom-dep:clsx AI (phantom-deps): Declared runtime dependency; used by cookie-consent components. ai
phantom-deps phantom-dep:@radix-ui/react-accordion AI (phantom-deps): Declared runtime dependency; used by Radix UI components. ai
phantom-deps phantom-dep:@radix-ui/react-switch AI (phantom-deps): Declared runtime dependency; used by Radix UI components. ai
phantom-deps phantom-dep:zustand AI (phantom-deps): Declared runtime dependency; used by cookie-consent state management. ai

Versions (showing 22 of 22)

Version Deps Published
2.1.2 5 / 8
2.1.1 5 / 8
2.1.0 5 / 8
2.0.4 5 / 8
2.0.3 5 / 7
2.0.2 5 / 7
2.0.1 5 / 7
2.0.0 5 / 7
1.0.0 5 / 7
0.1.13 5 / 7
0.1.12 5 / 7
0.1.11 5 / 7
0.1.10 5 / 7
0.1.9 5 / 7
0.1.8 5 / 6
0.1.7 5 / 6
0.1.6 2 / 3
0.1.5 2 / 3
0.1.4 2 / 3
0.1.3 2 / 3
0.1.2 2 / 3
0.1.1 2 / 3

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

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.

v2.1.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.

v2.0.4

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.

v2.0.3

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.

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

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

v0.1.1

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.