@unchainedshop/core-enrollments
Subscription and recurring billing module for the Unchained Engine
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@breejs/later | AI (dependencies): @breejs/later is a well-known cron/scheduler library; stable legitimate dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a security concern here. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/logger | AI (phantom-deps): Same-org sibling package listed as a dependency; phantom-dep heuristic false positive for this monorepo. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 3 / 2 | |
| 4.8.12 | 3 / 2 | |
| 4.8.11 | 3 / 2 | |
| 4.8.10 | 3 / 2 | |
| 4.8.9 | 3 / 2 | |
| 4.8.4 | 3 / 2 | |
| 4.8.3 | 3 / 2 | |
| 4.8.2 | 3 / 2 | |
| 4.8.1 | 3 / 2 | |
| 4.8.0 | 3 / 2 | |
| 4.7.2 | 3 / 2 | |
| 4.6.2 | 3 / 2 | |
| 4.6.1 | 3 / 2 | |
| 4.6.0 | 3 / 2 | |
| 4.5.0 | 3 / 2 | |
| 4.3.4 | 4 / 4 | |
| 4.3.2 | 4 / 4 | |
| 4.3.1 | 4 / 4 | |
| 4.1.3 | 4 / 4 | |
| 4.1.1 | 4 / 4 | |
| 4.0.2 | 4 / 4 | |
| 4.0.1 | 4 / 4 | |
| 4.0.0 | 4 / 4 |
v4.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v4.0.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.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.