@unchainedshop/core-files
File 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@unchainedshop/utils | AI (phantom-deps): Same-org monorepo scope; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped package in established monorepo; missing description is common for internal modules. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README typical of internal monorepo packages; not indicative of spam. | ai | |
| dependencies | unvetted-dep:@unchainedshop/file-upload | AI (dependencies): Same-org sibling dependency within the unchainedshop monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/logger | AI (phantom-deps): Same-org sibling declared as dependency; phantom-dep heuristic fires spuriously for this monorepo package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 4 / 2 | |
| 4.8.12 | 4 / 2 | |
| 4.8.11 | 4 / 2 | |
| 4.8.10 | 4 / 2 | |
| 4.8.9 | 4 / 2 | |
| 4.8.4 | 4 / 2 | |
| 4.8.3 | 4 / 2 | |
| 4.8.2 | 4 / 2 | |
| 4.8.1 | 4 / 2 | |
| 4.8.0 | 4 / 2 | |
| 4.7.2 | 3 / 2 | |
| 4.6.2 | 4 / 2 | |
| 4.6.1 | 4 / 2 | |
| 4.6.0 | 4 / 2 | |
| 4.5.0 | 4 / 2 | |
| 4.4.0 | 4 / 2 | |
| 4.3.4 | 4 / 3 | |
| 4.3.3 | 4 / 3 | |
| 4.3.2 | 4 / 3 | |
| 4.3.1 | 4 / 3 | |
| 4.3.0 | 4 / 3 | |
| 4.2.2 | 4 / 3 | |
| 4.2.1 | 4 / 3 | |
| 4.2.0 | 4 / 3 | |
| 4.1.3 | 4 / 3 | |
| 4.1.2 | 4 / 3 | |
| 4.1.1 | 4 / 3 | |
| 4.1.0 | 4 / 3 | |
| 4.0.2 | 4 / 3 | |
| 4.0.1 | 4 / 3 | |
| 4.0.0 | 4 / 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.