@entur/modal
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Entur org team rotation; consistent with org-managed design system package history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org context; routine maintainer handoff within Entur organization. | ai | |
| phantom-deps | phantom-dep:@entur/a11y | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on indirect/peer usage patterns common in design systems. | ai | |
| phantom-deps | phantom-dep:@entur/tokens | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.8.16 | 10 / 10 | |
| 1.8.15 | 10 / 10 | |
| 1.8.14 | 10 / 10 | |
| 1.8.13 | 10 / 10 | |
| 1.8.12 | 10 / 10 | |
| 1.8.11 | 10 / 10 | |
| 1.8.10 | 10 / 10 | |
| 1.8.9 | 10 / 10 | |
| 1.8.8 | 10 / 11 | |
| 1.8.7 | 10 / 11 | |
| 1.8.6 | 10 / 11 | |
| 1.8.5 | 10 / 11 | |
| 1.8.4 | 10 / 11 | |
| 1.8.3 | 10 / 11 | |
| 1.8.2 | 10 / 11 | |
| 1.8.1 | 10 / 11 | |
| 1.8.0 | 10 / 11 | |
| 1.7.79 | 10 / 11 | |
| 1.7.78 | 10 / 11 | |
| 1.7.77 | 10 / 11 | |
| 1.7.76 | 10 / 11 | |
| 1.7.75 | 10 / 11 | |
| 1.7.74 | 10 / 11 | |
| 1.7.73 | 10 / 11 | |
| 1.7.72 | 10 / 1 | |
| 1.7.71 | 10 / 1 | |
| 1.7.70 | 10 / 1 | |
| 1.7.69 | 10 / 1 | |
| 1.7.68 | 10 / 1 | |
| 1.7.67 | 10 / 1 | |
| 1.7.66 | 10 / 1 | |
| 1.7.65 | 10 / 1 | |
| 1.7.64 | 10 / 1 | |
| 1.7.63 | 10 / 1 | |
| 1.7.62 | 10 / 1 | |
| 1.7.61 | 10 / 1 | |
| 1.7.60 | 10 / 1 | |
| 1.7.59 | 10 / 1 | |
| 1.7.58 | 10 / 1 | |
| 1.7.57 | 10 / 0 | |
| 1.7.56 | 10 / 0 | |
| 1.7.55 | 10 / 0 | |
| 1.7.54 | 10 / 0 | |
| 1.7.53 | 10 / 0 | |
| 1.7.52 | 10 / 0 | |
| 1.7.51 | 10 / 0 | |
| 1.7.50 | 10 / 0 | |
| 1.7.49 | 10 / 0 | |
| 1.7.48 | 10 / 0 | |
| 1.7.47 | 10 / 0 | |
| 1.7.46 | 10 / 0 |
v1.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.66
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.
v1.7.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.63
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.
v1.7.62
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.
v1.7.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.59
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.
v1.7.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.48
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.
v1.7.47
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.
v1.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.