@entur-partner/common
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): tutturen is an established publisher (22 approved) within the entur org; transition appears legitimate. | ai | |
| license | copyleft-license:EUPL-1.2 | AI (license): EUPL-1.2 is the declared license; stable across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with clear purpose; missing description is benign for internal/partner libraries. | ai | |
| dependencies | unvetted-dep:@entur-partner/util | AI (dependencies): Same-org internal dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions from the official entur org; provenance absence is a process gap, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dependency in package.json; phantom-dep is a false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 11.3.0 | 2 / 9 | |
| 11.2.8 | 2 / 9 | |
| 11.2.7 | 2 / 9 | |
| 11.2.6 | 2 / 9 | |
| 11.2.5 | 2 / 9 | |
| 11.2.4 | 2 / 4 | |
| 11.2.3 | 2 / 4 | |
| 11.2.0 | 2 / 4 | |
| 11.1.3 | 2 / 4 | |
| 11.1.2 | 2 / 4 | |
| 11.1.1 | 2 / 4 | |
| 11.1.0 | 2 / 4 | |
| 11.0.1 | 2 / 4 | |
| 11.0.0 | 2 / 4 | |
| 10.0.3 | 2 / 4 | |
| 10.0.2 | 2 / 4 |
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.