@luigi-project/core Apache-2.0 12 versions

@luigi-project/core

npm Repository Homepage

Javascript library supporting consumers of the Luigi framework

12

Versions

Apache-2.0

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

hardlluigi-robotjohannesdoberer

Keywords

luigicoreUIextensibilitymicro-frontendsmicrofrontends

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped package @luigi-project/core is the legitimate core module of the SAP Luigi framework, not a typosquat of 'cors'. The namespace makes intent unambiguous; stable false positive across all versions.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): No-deps signal is expected for a pre-bundled library (ships luigi.js). Package is a mature, high-download framework module with 2133 versions; not spam.	ai	2026/04/25

Versions (showing 12 of 12)

Version	Deps	Published
2.30.0	0 / 0	2026-06-01
2.29.0	0 / 0	2026-03-19
2.28.0	0 / 0	2026-02-26
2.27.0	0 / 0	2026-02-09
2.26.0	0 / 0	2025-12-01
2.25.1	0 / 0	2025-10-22
2.25.0	0 / 0	2025-10-16
2.24.0	0 / 0	2025-09-18
2.23.1	0 / 0	2025-07-28
2.23.0	0 / 0	2025-07-23
2.22.1	0 / 0	2025-05-23
2.22.0	0 / 0	2025-05-20

v2.30.0

1 finding

LOW No provenance attestation provenance

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

v2.29.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@luigi-project/core' is 1 edit(s) away from popular package 'cors'.

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

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

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

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

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

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

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

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

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

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