@entur/expand
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is a known maintainer of this org package; no code changes from prior approved version. | ai | |
| phantom-deps | phantom-dep:@entur/tokens | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic misfires on bundled/transitive usage within @entur scope. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 3.7.12 | 6 / 11 | |
| 3.7.11 | 6 / 11 | |
| 3.7.10 | 6 / 11 | |
| 3.7.9 | 6 / 11 | |
| 3.7.8 | 6 / 11 | |
| 3.7.7 | 6 / 11 | |
| 3.7.6 | 6 / 11 | |
| 3.7.5 | 6 / 12 | |
| 3.7.4 | 6 / 12 | |
| 3.7.3 | 6 / 12 | |
| 3.7.2 | 6 / 12 | |
| 3.7.1 | 6 / 12 | |
| 3.7.0 | 6 / 12 | |
| 3.6.19 | 6 / 12 | |
| 3.6.18 | 6 / 12 | |
| 3.6.17 | 6 / 12 | |
| 3.6.16 | 6 / 12 | |
| 3.6.15 | 6 / 12 | |
| 3.6.14 | 6 / 12 | |
| 3.6.13 | 6 / 12 | |
| 3.6.12 | 6 / 2 | |
| 3.6.11 | 6 / 2 | |
| 3.6.10 | 6 / 2 | |
| 3.6.9 | 6 / 2 | |
| 3.6.8 | 6 / 2 | |
| 3.6.7 | 6 / 2 | |
| 3.6.6 | 6 / 2 | |
| 3.6.5 | 6 / 2 | |
| 3.6.4 | 6 / 2 | |
| 3.6.3 | 6 / 2 | |
| 3.6.2 | 6 / 2 | |
| 3.6.1 | 6 / 2 | |
| 3.6.0 | 6 / 2 | |
| 3.5.27 | 6 / 2 | |
| 3.5.26 | 6 / 2 | |
| 3.5.25 | 6 / 1 | |
| 3.5.24 | 6 / 1 | |
| 3.5.23 | 6 / 1 | |
| 3.5.22 | 6 / 1 | |
| 3.5.21 | 6 / 1 | |
| 3.5.20 | 6 / 1 | |
| 3.5.19 | 6 / 1 | |
| 3.5.18 | 6 / 1 | |
| 3.5.17 | 6 / 1 | |
| 3.5.16 | 6 / 1 | |
| 3.5.15 | 6 / 1 | |
| 3.5.14 | 6 / 1 | |
| 3.5.13 | 6 / 1 | |
| 3.5.12 | 6 / 1 |
v3.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-04-23, 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.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-03-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.
v3.6.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-03-05, 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.
v3.6.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-02-25, 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.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-01-15, 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.
v3.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2024-07-11, 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.
v3.5.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2024-07-11, 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.
v3.5.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2024-06-11, 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.
v3.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.