← Home

@callstack/react-theme-provider

npm Repository Homepage

Theme provider for react and react-native applications

9
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

admin-callstackrafikitikijbindamdjastrzebskisouhethymikeegrabbousatya164

Keywords

reactreact-nativethemeprovider

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Callstack org maintainer rotation, no code changes accompanying it. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with org maintainer handoff, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Stable package with infrequent releases; no suspicious content change. ai

Versions (showing 9 of 9)

Version Deps Published
3.0.9 2 / 16
3.0.8 2 / 16
3.0.7 2 / 16
3.0.6 2 / 16
3.0.5 2 / 16
3.0.3 3 / 16
3.0.2 3 / 16
3.0.1 2 / 17
3.0.0 2 / 16

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.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.