@unchainedshop/core-warehousing
Inventory and stock management 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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established unchainedshop monorepo package; no material changes vs prior version, publisher has clean track record. | ai | |
| dependencies | unvetted-dep:expiry-map | AI (dependencies): expiry-map is a small, stable utility with no known advisories; acceptable for this package. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/utils | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic unreliable for monorepo transitive usage. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/logger | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic unreliable for monorepo transitive usage. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 5 / 2 | |
| 4.8.12 | 5 / 2 | |
| 4.8.11 | 5 / 2 | |
| 4.8.10 | 5 / 2 | |
| 4.8.9 | 5 / 2 | |
| 4.6.0 | 5 / 2 | |
| 4.2.0 | 5 / 3 | |
| 4.1.3 | 5 / 3 | |
| 4.1.2 | 5 / 3 | |
| 4.0.1 | 5 / 3 | |
| 4.0.0 | 5 / 3 |
v4.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.