@rango-dev/widget-embedded MIT 25 versions

@rango-dev/widget-embedded

npm

Rango Embedded Widget

25

Versions

MIT

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

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:shady-links-tlds	AI (semgrep): URLs are Cosmos/Umee blockchain RPC endpoints in a mock data file, not C2 infrastructure.	ai	2026/04/30
phantom-deps	phantom-dep:immer	AI (phantom-deps): Likely used transitively or in config; stable false positive for this monorepo package.	ai	2026/04/30
phantom-deps	phantom-dep:ethers	AI (phantom-deps): Likely used transitively or in config; stable false positive for this monorepo package.	ai	2026/04/30
phantom-deps	phantom-dep:values.js	AI (phantom-deps): Stable false positive; referenced in config files per finding.	ai	2026/04/30
phantom-deps	phantom-dep:@lingui/react	AI (phantom-deps): Stable false positive; referenced in config files per finding.	ai	2026/04/30
phantom-deps	phantom-dep:copy-to-clipboard	AI (phantom-deps): Stable false positive; referenced in config files per finding.	ai	2026/04/30

Versions (showing 25 of 25)

Version	Deps	Published
0.60.1	27 / 4	2026-06-02
0.60.0	27 / 4	2026-05-31
0.59.1	24 / 0	2026-05-02
0.59.0	24 / 0	2026-04-29
0.58.0	24 / 0	2025-12-30
0.57.0	24 / 0	2025-12-15
0.56.0	24 / 0	2025-12-09
0.55.0	24 / 0	2025-12-02
0.54.1	24 / 0	2025-11-22
0.52.0	24 / 0	2025-10-29
0.51.0	24 / 0	2025-09-29
0.50.0	24 / 0	2025-09-06
0.49.0	24 / 0	2025-08-27
0.48.0	24 / 0	2025-08-19
0.47.0	24 / 0	2025-08-05
0.46.1	24 / 0	2025-07-27
0.46.0	24 / 0	2025-07-22
0.45.0	24 / 0	2025-07-09
0.44.1	24 / 0	2025-06-10
0.44.0	24 / 0	2025-06-09
0.43.0	24 / 0	2025-05-26
0.42.3	24 / 0	2025-05-21
0.42.2	24 / 0	2025-05-12
0.42.1	24 / 0	2025-05-04
0.42.0	24 / 0	2025-04-30

v0.60.1

1 finding

LOW No provenance attestation provenance

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

v0.60.0

1 finding

LOW No provenance attestation provenance

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

v0.59.1

1 finding

LOW No provenance attestation provenance

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

v0.58.0

1 finding

LOW No provenance attestation provenance

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

v0.57.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.56.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.55.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.54.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.

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

1 finding

LOW No provenance attestation provenance

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

v0.50.0

1 finding

LOW No provenance attestation provenance

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

v0.49.0

1 finding

LOW No provenance attestation provenance

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

v0.48.0

1 finding

LOW No provenance attestation provenance

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

v0.47.0

1 finding

LOW No provenance attestation provenance

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

v0.46.1

1 finding

LOW No provenance attestation provenance

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

v0.46.0

1 finding

LOW No provenance attestation provenance

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

v0.45.0

1 finding

LOW No provenance attestation provenance

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

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

v0.44.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.43.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.42.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.42.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.42.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.

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