@entur/alert
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-removed | AI (maintainer-change): Entur org package with active publishing history; maintainer rotation is routine for this org. | ai | |
| phantom-deps | phantom-dep:@entur/tokens | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.19.4 | 9 / 10 | |
| 0.19.3 | 9 / 10 | |
| 0.19.2 | 9 / 10 | |
| 0.19.1 | 9 / 10 | |
| 0.19.0 | 9 / 10 | |
| 0.18.11 | 9 / 10 | |
| 0.18.10 | 9 / 10 | |
| 0.18.9 | 9 / 10 | |
| 0.18.8 | 9 / 11 | |
| 0.18.7 | 9 / 11 | |
| 0.18.6 | 9 / 11 | |
| 0.18.5 | 9 / 11 | |
| 0.18.4 | 9 / 11 | |
| 0.18.3 | 9 / 11 | |
| 0.18.2 | 9 / 11 | |
| 0.18.1 | 9 / 11 | |
| 0.18.0 | 9 / 11 | |
| 0.17.19 | 9 / 11 | |
| 0.17.18 | 9 / 11 | |
| 0.17.17 | 9 / 11 | |
| 0.17.16 | 9 / 11 | |
| 0.17.15 | 9 / 11 | |
| 0.17.14 | 9 / 11 | |
| 0.17.13 | 9 / 11 | |
| 0.17.12 | 9 / 1 | |
| 0.17.11 | 9 / 1 | |
| 0.17.10 | 9 / 1 | |
| 0.17.9 | 9 / 1 | |
| 0.17.8 | 9 / 1 | |
| 0.17.7 | 9 / 1 | |
| 0.17.6 | 9 / 1 | |
| 0.17.5 | 9 / 1 | |
| 0.17.4 | 9 / 1 | |
| 0.17.3 | 9 / 1 | |
| 0.17.2 | 9 / 1 | |
| 0.17.1 | 9 / 1 | |
| 0.17.0 | 9 / 1 | |
| 0.16.24 | 9 / 1 | |
| 0.16.23 | 9 / 1 | |
| 0.16.22 | 9 / 0 | |
| 0.16.21 | 9 / 0 | |
| 0.16.20 | 9 / 0 | |
| 0.16.19 | 9 / 0 | |
| 0.16.18 | 9 / 0 | |
| 0.16.17 | 9 / 0 | |
| 0.16.16 | 9 / 0 | |
| 0.16.15 | 9 / 0 | |
| 0.16.14 | 9 / 0 | |
| 0.16.13 | 9 / 0 | |
| 0.16.12 | 9 / 0 | |
| 0.16.11 | 9 / 0 |
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.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.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.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.
v0.17.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.
v0.17.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.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.24
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.
v0.16.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.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 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.