@entur-partner/util
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate org package, no behavioral change, publisher has clean track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with publisher transition on established Entur package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @entur-partner org package; name similarity to uuid is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 1 / 4 | |
| 1.3.11 | 1 / 4 | |
| 1.3.10 | 1 / 1 | |
| 1.3.8 | 1 / 1 | |
| 1.3.7 | 1 / 1 | |
| 1.3.6 | 1 / 1 | |
| 1.3.5 | 1 / 1 | |
| 1.3.4 | 1 / 1 | |
| 1.3.3 | 1 / 1 | |
| 1.3.2 | 1 / 1 | |
| 1.3.1 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.4 | 1 / 1 | |
| 1.2.3 | 1 / 1 | |
| 1.2.1 | 1 / 1 |
v1.2.4
2 findingsThis version was published by a different npm account than previous versions on 2025-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
2 findingsThis version was published by a different npm account than previous versions on 2025-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.