@vitality-ds/icons ISC 12 versions

@vitality-ds/icons

npm Repository Homepage

Gentu icons

12

Versions

ISC

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

lucas.arundellgeniesolutionsadminxanderangelladrianaheeshxiaochi-limag-ken-sully

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped design-system package; Levenshtein match to 'cors' is a false positive across all versions.	ai	2026/04/29
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom is a peer/runtime dep for a React component library; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:prop-types	AI (phantom-deps): prop-types is a standard React companion dep; stable false positive for this package.	ai	2026/04/29

Versions (showing 12 of 12)

Version	Deps	Published
5.7.0	5 / 12	2026-05-25
5.6.3	5 / 12	2026-03-12
5.5.0	5 / 12	2026-01-12
5.4.0	5 / 12	2025-12-09
5.3.0	5 / 12	2025-11-12
5.2.1	5 / 12	2025-11-05
5.2.0	5 / 12	2025-10-09
5.1.1	5 / 12	2025-09-29
5.1.0	5 / 12	2025-09-29
5.0.4	5 / 12	2025-09-18
5.0.3	5 / 12	2025-09-18
5.0.2	5 / 12	2025-09-15

v5.7.0

1 finding

LOW No provenance attestation provenance

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

v5.6.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.

v5.5.0

1 finding

LOW No provenance attestation provenance

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

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

v5.3.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.

v5.2.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.

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.1.0

1 finding

LOW No provenance attestation provenance

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

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

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

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