@rip-lang/ui No license 37 versions

@rip-lang/ui

npm

Unified UI system for Rip — browser widgets, email components, and Tailwind integration

37

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

shreeve

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get used in a Proxy Symbol-passthrough handler — idiomatic reactive framework pattern, not evasion.	ai	2026/05/20
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @rip-lang package; not a plausible typosquat of pg.	ai	2026/04/29
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @rip-lang package; not a plausible typosquat of qs.	ai	2026/04/29
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped @rip-lang package; not a plausible typosquat of uuid.	ai	2026/04/29
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped @rip-lang package; not a plausible typosquat of yup.	ai	2026/04/29
phantom-deps	phantom-dep:rip-lang	AI (phantom-deps): rip-lang is a runtime/language dependency referenced in config; .rip files are the source format, not JS imports.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @rip-lang package; not a plausible typosquat of joi.	ai	2026/04/29

Versions (showing 37 of 37)

Version	Deps	Published
0.4.23	3 / 3	2026-04-27
0.4.22	3 / 3	2026-04-24
0.4.21	3 / 3	2026-04-23
0.4.20	3 / 3	2026-04-23
0.4.19	3 / 3	2026-04-23
0.4.18	3 / 3	2026-04-20
0.4.17	3 / 3	2026-04-20
0.4.16	3 / 3	2026-04-10
0.4.15	3 / 3	2026-04-10
0.4.14	3 / 3	2026-04-10
0.4.13	3 / 3	2026-04-04
0.4.12	3 / 3	2026-04-04
0.4.11	3 / 3	2026-04-04
0.4.10	3 / 3	2026-04-02
0.3.20	0 / 0	2026-02-21
0.3.19	0 / 0	2026-02-20
0.3.18	0 / 0	2026-02-20
0.3.17	0 / 0	2026-02-20
0.3.16	0 / 0	2026-02-20
0.3.15	0 / 0	2026-02-20
0.3.14	0 / 0	2026-02-19
0.3.13	0 / 0	2026-02-19
0.3.12	0 / 0	2026-02-19
0.3.11	0 / 0	2026-02-19
0.3.10	0 / 0	2026-02-19
0.3.9	0 / 0	2026-02-19
0.3.8	1 / 0	2026-02-19
0.3.7	1 / 0	2026-02-19
0.3.6	1 / 0	2026-02-19
0.3.5	1 / 0	2026-02-19
0.3.4	1 / 0	2026-02-19
0.3.3	1 / 0	2026-02-19
0.3.2	1 / 0	2026-02-18
0.3.0	1 / 0	2026-02-12
0.1.3	1 / 0	2026-02-09
0.1.2	1 / 0	2026-02-08
0.1.1	1 / 0	2026-02-08

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

1 finding

LOW No provenance attestation provenance

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

v0.4.14

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.19

1 finding

LOW No provenance attestation provenance

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

v0.3.18

1 finding

LOW No provenance attestation provenance

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

v0.3.17

1 finding

LOW No provenance attestation provenance

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

v0.3.16

1 finding

LOW No provenance attestation provenance

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

v0.3.15

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

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

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

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

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

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