@embeddable.com/react No license 19 versions

@embeddable.com/react

npm Repository Homepage

19

Versions

—

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

tom-embeddableruiribeiromisha_terevgeny-embeddablejozef_trevorsyed1995yashrajk17hjkmarshallako-hk

Keywords

embeddablereact

Versions (showing 19 of 19)

Version	Deps	Published
2.13.7	1 / 9	2026-05-04
2.13.6	1 / 9	2026-03-30
2.13.5	1 / 9	2026-02-27
2.13.4	1 / 8	2026-02-18
2.13.3	1 / 6	2026-02-09
2.13.2	1 / 6	2026-02-04
2.13.1	1 / 6	2026-01-28
2.13.0	1 / 6	2026-01-08
2.12.3	1 / 6	2025-12-17
2.12.2	1 / 6	2025-12-12
2.12.1	1 / 6	2025-12-09
2.12.0	1 / 6	2025-10-23
2.10.9	1 / 6	2025-08-05
2.10.8	1 / 6	2025-07-15
2.10.6	1 / 6	2025-07-07
2.10.5	1 / 2	2025-06-24
2.10.4	1 / 2	2025-06-16
2.10.3	1 / 2	2025-05-28
2.10.2	1 / 2	2025-05-15

v2.13.7

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

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ako-hk → ruiribeiro (on 2026-03-30, known maintainer) provenance

This version was published by a different npm account (ruiribeiro) than the most recent previously approved version (ako-hk) on 2026-03-30, but ruiribeiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ako-hk → ruiribeiro (on 2026-02-27, known maintainer) provenance

This version was published by a different npm account (ruiribeiro) than the most recent previously approved version (ako-hk) on 2026-02-27, but ruiribeiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ako-hk → yashrajk17 (on 2026-02-18, known maintainer) provenance

This version was published by a different npm account (yashrajk17) than the most recent previously approved version (ako-hk) on 2026-02-18, but yashrajk17 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: syed1995 → ako-hk (on 2026-02-09, known maintainer) provenance

This version was published by a different npm account (ako-hk) than the most recent previously approved version (syed1995) on 2026-02-09, but ako-hk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: syed1995 → ako-hk (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (ako-hk) than the most recent previously approved version (syed1995) on 2026-02-04, but ako-hk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ruiribeiro → syed1995 (on 2026-01-08, known maintainer) provenance

This version was published by a different npm account (syed1995) than the most recent previously approved version (ruiribeiro) on 2026-01-08, but syed1995 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.12.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: evgeny-embeddable → syed1995 (on 2025-12-17, known maintainer) provenance

This version was published by a different npm account (syed1995) than the most recent previously approved version (evgeny-embeddable) on 2025-12-17, but syed1995 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.12.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: evgeny-embeddable → ruiribeiro (on 2025-12-12, known maintainer) provenance

This version was published by a different npm account (ruiribeiro) than the most recent previously approved version (evgeny-embeddable) on 2025-12-12, but ruiribeiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.12.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: evgeny-embeddable → syed1995 (on 2025-12-09, known maintainer) provenance

This version was published by a different npm account (syed1995) than the most recent previously approved version (evgeny-embeddable) on 2025-12-09, but syed1995 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.12.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: evgeny-embeddable → ruiribeiro (on 2025-10-23, known maintainer) provenance

This version was published by a different npm account (ruiribeiro) than the most recent previously approved version (evgeny-embeddable) on 2025-10-23, but ruiribeiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.10.9

1 finding

LOW No provenance attestation provenance

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

v2.10.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: evgeny-embeddable → syed1995 (on 2025-07-15, known maintainer) provenance

This version was published by a different npm account (syed1995) than the most recent previously approved version (evgeny-embeddable) on 2025-07-15, but syed1995 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.10.6

1 finding

LOW No provenance attestation provenance

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

v2.10.5

2 findings

HIGH Publisher changed: evgeny-embeddable → syed1995 (on 2025-06-24) provenance

This version was published by a different npm account than previous versions on 2025-06-24. 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.10.4

1 finding

LOW No provenance attestation provenance

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

v2.10.3

1 finding

LOW No provenance attestation provenance

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

v2.10.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.