← Home

@central-icons-react-native/round-outlined-radius-2-stroke-1

A collection of round outlined React icons with 2px radius and 1px stroke width, designed for use in React Native / Expo applications.

17
Versions
SEE LICENSE IN LICENSE.md
License
Yes
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

tamino-martinius

Keywords

reactreact-nativeexpoiconssvguidesign-systemsharproundfilledoutlinedstrokeradiuscentral-iconsicon-libraryicon-pack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:IconSettingsGear4/index.js AI (source-diff): tsup-bundled icon component; minified single-line output is normal for this icon library's build pipeline. ai
source-diff large-new-source-files AI (source-diff): Icon library regularly adds new icon files across versions; large file additions are expected and benign. ai
install-scripts install-script:preinstall AI (install-scripts): License check script is consistent with commercial icon library's custom license enforcement; stable pattern across 235 versions. ai

Versions (showing 17 of 17)

Version Deps Published
1.1.234 1 / 5
1.1.232 1 / 5
1.1.228 1 / 5
1.1.226 1 / 5
1.1.225 1 / 5
1.1.223 1 / 5
1.1.222 1 / 5
1.1.221 1 / 5
1.1.220 1 / 5
1.1.219 1 / 5
1.1.218 1 / 5
1.1.217 1 / 5
1.1.216 1 / 5
1.1.193 1 / 5
1.1.183 1 / 5
1.1.180 1 / 5
1.1.178 1 / 5

v1.1.234

2 findings
HIGH New obfuscated file: IconSettingsGear4/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.1.232

1 finding
LOW No provenance attestation provenance

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

v1.1.228

1 finding
LOW No provenance attestation provenance

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

v1.1.226

1 finding
LOW No provenance attestation provenance

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

v1.1.225

1 finding
LOW No provenance attestation provenance

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

v1.1.223

1 finding
LOW No provenance attestation provenance

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

v1.1.222

1 finding
LOW No provenance attestation provenance

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

v1.1.221

1 finding
LOW No provenance attestation provenance

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

v1.1.220

1 finding
LOW No provenance attestation provenance

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

v1.1.219

1 finding
LOW No provenance attestation provenance

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

v1.1.218

1 finding
LOW No provenance attestation provenance

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

v1.1.217

1 finding
LOW No provenance attestation provenance

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

v1.1.193

1 finding
LOW No provenance attestation provenance

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

v1.1.183

1 finding
LOW No provenance attestation provenance

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

v1.1.180

1 finding
LOW No provenance attestation provenance

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

v1.1.178

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.