← Home

@versini/ui-icon-renderer

npm Repository Homepage

[![npm version](https://img.shields.io/npm/v/@versini/ui-icon-renderer?style=flat-square)](https://www.npmjs.com/package/@versini/ui-icon-renderer) ![npm package minimized gzipped size](<https://img.shields.io/bundlejs/size/%40versini%2Fui-icon-renderer?s

15
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

aversini

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal npm account to GitHub Actions CI/CD matches the repo owner; consistent with automation adoption. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Part of aversini's established UI component monorepo; 0.0.0 is a legitimate initial release pattern here. ai
bogus-package bogus-package AI (bogus-package): Sparse metadata is consistent with early-stage monorepo package from a known publisher with 11 approved packages. ai

Versions (showing 15 of 15)

Version Deps Published
2.5.0 0 / 1
2.4.0 0 / 1
2.3.2 0 / 0
2.3.1 0 / 0
2.3.0 0 / 0
2.2.0 0 / 0
2.1.1 0 / 0
2.1.0 0 / 0
2.0.0 0 / 0
1.0.4 0 / 0
1.0.3 0 / 0
1.0.2 1 / 0
1.0.1 0 / 1
1.0.0 0 / 1
0.0.0 0 / 1

v2.5.0

2 findings
HIGH Publisher changed: aversini → GitHub Actions (on 2026-05-22) provenance

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

LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

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

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

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

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

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

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