← Home

@entur/loader

npm Repository Homepage
20
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

oysvalenturaskentandersentestowermagnusrandtysseng-enturfrankwaldalceciliehrrteamplattformkennethngo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Entur org team restructuring; teamplattform is an org-internal team account, not an external takeover signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of wfeiring consistent with org team rotation; no malicious indicators present. ai
publish-pattern dormant-publish AI (publish-pattern): Established design-system package; dormancy reflects normal release cadence, not takeover. ai
dependencies unvetted-dep:@entur/utils AI (dependencies): Same org scope (@entur); stable internal dependency across many versions of this package. ai
phantom-deps phantom-dep:@entur/tokens AI (phantom-deps): @entur/tokens is a same-org dependency listed in package.json; phantom-dep heuristic is a false positive here. ai

Versions (showing 20 of 20)

Version Deps Published
0.7.0 4 / 10
0.6.7 4 / 10
0.6.6 4 / 10
0.6.5 4 / 11
0.6.4 4 / 11
0.6.3 4 / 11
0.6.2 4 / 11
0.6.1 4 / 11
0.6.0 4 / 11
0.5.36 4 / 11
0.5.35 4 / 11
0.5.34 4 / 11
0.5.33 4 / 11
0.5.32 4 / 11
0.5.31 4 / 11
0.5.30 4 / 11
0.5.29 4 / 1
0.5.28 4 / 1
0.5.27 4 / 1
0.5.26 4 / 1

v0.7.0

1 finding
LOW No provenance attestation provenance

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

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

v0.6.6

1 finding
LOW No provenance attestation provenance

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

v0.6.5

1 finding
LOW No provenance attestation provenance

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

v0.6.4

1 finding
LOW No provenance attestation provenance

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

v0.6.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: ceciliehrr → magnusrand (on 2026-01-28, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2026-01-28, but magnusrand 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.

v0.6.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: ceciliehrr → magnusrand (on 2026-01-23, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2026-01-23, but magnusrand 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.

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.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: ceciliehrr → magnusrand (on 2025-12-05, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-12-05, but magnusrand 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.

v0.5.36

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: ceciliehrr → magnusrand (on 2025-11-24, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-11-24, but magnusrand 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.

v0.5.35

1 finding
LOW No provenance attestation provenance

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

v0.5.34

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: magnusrand → ceciliehrr (on 2025-10-17, known maintainer) provenance

This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-10-17, but ceciliehrr 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.

v0.5.33

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: ceciliehrr → magnusrand (on 2025-09-30, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-09-30, but magnusrand 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.

v0.5.32

1 finding
LOW No provenance attestation provenance

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

v0.5.31

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: ceciliehrr → magnusrand (on 2025-09-03, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-09-03, but magnusrand 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.

v0.5.30

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: ceciliehrr → magnusrand (on 2025-08-29, known maintainer) provenance

This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-08-29, but magnusrand 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.

v0.5.29

1 finding
LOW No provenance attestation provenance

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

v0.5.28

1 finding
LOW No provenance attestation provenance

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

v0.5.27

1 finding
LOW No provenance attestation provenance

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

v0.5.26

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.