← Home

@project-lary/react-material-symbols-300-sharp

npm Repository Homepage

Latest sharp React icon components with weight 300 for Material Symbols

6
Versions
Apache-2.0
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

selcuklaryflachealiprojectlary

Keywords

lary-material-symbolsreactreact-iconsreact-material-symbolsmaterial-symbolsmaterial-iconsmaterial-designmaterialsymbolsicons

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/components/ModeFan2Filled.js AI (source-diff): Long line is a single SVG path string in a generated icon component, not obfuscation. ai
source-diff large-new-source-files AI (source-diff): Icon library adds many generated per-icon component files; expected pattern. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher has 18 approved packages under this project-lary org, no rejects. ai

Versions (showing 6 of 6)

Version Deps Published
0.39.0 0 / 0
0.38.0 0 / 0
0.37.0 0 / 0
0.36.0 0 / 0
0.35.0 0 / 0
0.34.0 0 / 0

v0.36.0

3 findings
HIGH Publisher changed: selcuklary → aliprojectlary (on 2026-03-15) provenance

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

HIGH New obfuscated file: dist/components/ModeFan2Filled.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.

v0.35.0

1 finding
LOW No provenance attestation provenance

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

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