@unchainedshop/ticketing
Event ticketing extension for the Unchained Engine with PDF and wallet pass support
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; no provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@unchainedshop/api | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@unchainedshop/core | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@unchainedshop/mongodb | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@unchainedshop/core-files | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@unchainedshop/core-worker | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@unchainedshop/core-warehousing | AI (dependencies): Sibling package in the same unchainedshop monorepo; stable false positive. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.8.11 | 8 / 5 | |
| 4.8.10 | 8 / 5 | |
| 4.8.9 | 8 / 5 | |
| 4.8.8 | 8 / 5 | |
| 4.8.7 | 8 / 5 | |
| 4.8.6 | 8 / 5 | |
| 4.8.5 | 8 / 5 | |
| 4.8.4 | 8 / 5 | |
| 4.8.3 | 8 / 5 | |
| 4.8.2 | 8 / 5 | |
| 4.8.1 | 8 / 5 | |
| 4.8.0 | 8 / 5 | |
| 4.6.2 | 8 / 5 | |
| 4.6.1 | 8 / 5 | |
| 4.6.0 | 8 / 5 | |
| 4.5.0 | 8 / 5 | |
| 4.4.0 | 8 / 5 | |
| 4.3.4 | 8 / 5 | |
| 4.3.3 | 8 / 5 | |
| 4.3.2 | 8 / 5 | |
| 4.3.1 | 8 / 5 | |
| 4.3.0 | 8 / 5 | |
| 4.2.0 | 8 / 5 | |
| 4.1.3 | 8 / 5 | |
| 4.1.2 | 8 / 5 | |
| 4.1.1 | 8 / 5 | |
| 4.1.0 | 8 / 5 | |
| 4.0.2 | 8 / 5 | |
| 4.0.1 | 8 / 5 | |
| 4.0.0 | 8 / 5 |
v4.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.