ra-language-english MIT 35 versions

ra-language-english

npm Repository Homepage

English messages for react-admin, the frontend framework for building admin applications on top of REST/GraphQL services

35

Versions

MIT

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

fzaninottothieryslax57

Keywords

reactreact-adminadmin-on-resttranslation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): slax57 is a marmelab contributor with prior approved publishes; team rotation within the react-admin org.	ai	2026/05/04
publish-pattern	dormant-publish	AI (publish-pattern): Large monorepo; individual sub-packages can go dormant between releases without indicating takeover.	ai	2026/05/04
dependencies	unvetted-dep:ra-core	AI (dependencies): ra-core is a sibling package in the same react-admin monorepo; dependency is expected and stable across versions.	ai	2026/04/29

Versions (showing 35 of 35)

Version	Deps	Published
5.14.7	1 / 2	2026-05-18
5.14.6	1 / 2	2026-04-21
5.14.5	1 / 2	2026-03-31
5.14.4	1 / 2	2026-03-10
5.14.3	1 / 2	2026-02-27
5.14.2	1 / 2	2026-02-16
5.14.1	1 / 2	2026-01-30
5.14.0	1 / 2	2026-01-23
5.13.6	1 / 2	2026-01-16
5.13.5	1 / 2	2026-01-09
5.13.4	1 / 2	2025-12-16
5.13.3	1 / 2	2025-12-05
5.13.2	1 / 2	2025-11-21
5.13.1	1 / 2	2025-11-14
5.13.0	1 / 2	2025-11-13
5.12.3	1 / 2	2025-11-03
5.12.2	1 / 2	2025-10-24
5.12.1	1 / 2	2025-10-17
5.12.0	1 / 2	2025-10-07
5.11.4	1 / 2	2025-09-26
5.11.3	1 / 2	2025-09-19
5.11.2	1 / 2	2025-09-15
5.11.1	1 / 2	2025-09-05
5.11.0	1 / 2	2025-09-03
5.10.2	1 / 2	2025-08-25
5.10.1	1 / 2	2025-08-01
5.10.0	1 / 2	2025-07-22
5.9.2	1 / 2	2025-07-15
5.9.1	1 / 2	2025-07-03
5.9.0	1 / 2	2025-06-23
5.8.4	1 / 2	2025-06-16
5.8.3	1 / 2	2025-05-28
5.8.2	1 / 2	2025-05-16
5.8.1	1 / 2	2025-05-12
5.8.0	1 / 2	2025-04-30

v5.14.7

1 finding

LOW No provenance attestation provenance

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

v5.14.5

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

2 findings

HIGH Publisher changed: djhi → slax57 (on 2026-03-10) provenance

This version was published by a different npm account than previous versions on 2026-03-10. 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.

v5.14.3

2 findings

HIGH Publisher changed: djhi → slax57 (on 2026-02-27) provenance

This version was published by a different npm account than previous versions on 2026-02-27. 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.

v5.14.2

2 findings

HIGH Publisher changed: djhi → slax57 (on 2026-02-16) provenance

This version was published by a different npm account than previous versions on 2026-02-16. 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.

v5.14.1

2 findings

HIGH Publisher changed: djhi → slax57 (on 2026-01-30) provenance

This version was published by a different npm account than previous versions on 2026-01-30. 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.

v5.14.0

2 findings

HIGH Publisher changed: djhi → slax57 (on 2026-01-23) provenance

This version was published by a different npm account than previous versions on 2026-01-23. 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.

v5.13.6

1 finding

LOW No provenance attestation provenance

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

v5.13.5

1 finding

LOW No provenance attestation provenance

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

v5.13.4

1 finding

LOW No provenance attestation provenance

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

v5.13.3

1 finding

LOW No provenance attestation provenance

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

v5.13.2

1 finding

LOW No provenance attestation provenance

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

v5.13.1

2 findings

HIGH Publisher changed: djhi → slax57 (on 2025-11-14) provenance

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

v5.13.0

2 findings

HIGH Publisher changed: djhi → slax57 (on 2025-11-13) provenance

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

v5.12.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.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: slax57 → djhi (on 2025-10-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-24. This could indicate a legitimate maintainer transition or an account compromise.

v5.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: djhi → slax57 (on 2025-10-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-17. This could indicate a legitimate maintainer transition or an account compromise.

v5.12.0

1 finding

LOW No provenance attestation provenance

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

v5.11.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: slax57 → djhi (on 2025-09-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-26. This could indicate a legitimate maintainer transition or an account compromise.

v5.11.3

1 finding

LOW No provenance attestation provenance

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

v5.11.2

1 finding

LOW No provenance attestation provenance

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

v5.11.1

1 finding

LOW No provenance attestation provenance

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

v5.11.0

1 finding

LOW No provenance attestation provenance

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

v5.10.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: djhi → slax57 (on 2025-08-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-25. This could indicate a legitimate maintainer transition or an account compromise.

v5.10.1

1 finding

LOW No provenance attestation provenance

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

v5.10.0

1 finding

LOW No provenance attestation provenance

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

v5.9.2

1 finding

LOW No provenance attestation provenance

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

v5.9.1

1 finding

LOW No provenance attestation provenance

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

v5.9.0

1 finding

LOW No provenance attestation provenance

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

v5.8.4

1 finding

LOW No provenance attestation provenance

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

v5.8.3

1 finding

LOW No provenance attestation provenance

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

v5.8.2

1 finding

LOW No provenance attestation provenance

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

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