@entur/layout
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Long-lived org package with active maintainer rotation; removal of carljoachim is routine housekeeping. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component; missing description is a cosmetic issue, not a risk signal. | ai | |
| phantom-deps | phantom-dep:@entur/tokens | AI (phantom-deps): Same-org sibling dep; declared in dependencies, phantom-dep heuristic false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 5 / 10 | |
| 3.7.0 | 5 / 10 | |
| 3.6.1 | 5 / 10 | |
| 3.6.0 | 5 / 10 | |
| 3.5.0 | 5 / 11 | |
| 3.4.2 | 5 / 11 | |
| 3.4.1 | 5 / 11 | |
| 3.4.0 | 5 / 11 | |
| 3.3.3 | 5 / 11 | |
| 3.3.2 | 5 / 11 | |
| 3.3.1 | 5 / 11 | |
| 3.3.0 | 5 / 11 | |
| 3.2.3 | 5 / 11 | |
| 3.2.2 | 5 / 11 | |
| 3.2.1 | 5 / 11 | |
| 3.2.0 | 5 / 11 | |
| 3.1.11 | 5 / 11 | |
| 3.1.10 | 5 / 11 | |
| 3.1.9 | 5 / 11 | |
| 3.1.8 | 5 / 1 | |
| 3.1.7 | 5 / 1 | |
| 3.1.6 | 5 / 1 | |
| 3.1.5 | 5 / 1 |
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
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-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.
v3.2.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 (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.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
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-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.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
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-09-24, 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.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.