@descope-ui/descope-tooltip No license 19 versions

@descope-ui/descope-tooltip

npm

19

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

omercnetnirgur

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New dep is a same-org sibling at matching version, consistent with coordinated monorepo releases.	ai	2026/05/12
dependencies	unvetted-dep:@descope-ui/descope-anchored	AI (dependencies): Same-namespace sibling package at matching version; consistent with monorepo component extraction.	ai	2026/05/12
bogus-package	bogus-package	AI (bogus-package): Part of @descope-ui monorepo; missing metadata is a style issue, not a spam/malware indicator for this established package family.	ai	2026/04/28
npm-metadata	no-description	AI (npm-metadata): Monorepo component package; missing description is consistent across the family and not a risk signal.	ai	2026/04/28

Versions (showing 19 of 124)

Version	Deps	Published
2.2.31	4 / 2	2026-01-21
2.2.30	4 / 2	2026-01-19
2.2.29	4 / 2	2026-01-19
2.2.28	4 / 2	2026-01-19
2.2.27	4 / 2	2026-01-18
2.2.26	4 / 2	2026-01-18
2.2.25	4 / 2	2026-01-15
2.2.24	4 / 2	2026-01-13
2.2.23	4 / 2	2026-01-13
2.2.22	4 / 2	2026-01-13
2.2.21	4 / 2	2026-01-12
2.2.20	4 / 2	2026-01-12
2.2.19	4 / 2	2026-01-11
2.2.18	4 / 2	2026-01-06
2.2.17	4 / 2	2026-01-05
2.2.16	4 / 2	2025-12-28
2.2.15	4 / 2	2025-12-23
2.2.14	4 / 2	2025-12-22
2.2.13	4 / 2	2025-12-21

v2.2.31

1 finding

LOW No provenance attestation provenance

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

v2.2.30

1 finding

LOW No provenance attestation provenance

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

v2.2.29

1 finding

LOW No provenance attestation provenance

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

v2.2.28

1 finding

LOW No provenance attestation provenance

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

v2.2.27

1 finding

LOW No provenance attestation provenance

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

v2.2.26

1 finding

LOW No provenance attestation provenance

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

v2.2.25

1 finding

LOW No provenance attestation provenance

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

v2.2.24

1 finding

LOW No provenance attestation provenance

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

v2.2.23

1 finding

LOW No provenance attestation provenance

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

v2.2.22

1 finding

LOW No provenance attestation provenance

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

v2.2.21

1 finding

LOW No provenance attestation provenance

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

v2.2.20

1 finding

LOW No provenance attestation provenance

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

v2.2.19

1 finding

LOW No provenance attestation provenance

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

v2.2.18

1 finding

LOW No provenance attestation provenance

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

v2.2.17

1 finding

LOW No provenance attestation provenance

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

v2.2.16

1 finding

LOW No provenance attestation provenance

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

v2.2.15

1 finding

LOW No provenance attestation provenance

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

v2.2.14

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.

v2.2.13

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.