@unchainedshop/core-filters
Product filtering and search 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 |
|---|---|---|---|---|
| license | copyleft-license:EUPL-1.2 | AI (license): EUPL-1.2 is the declared license; stable for this package. | ai | |
| dependencies | unvetted-dep:expiry-map | AI (dependencies): expiry-map is a well-known utility; stable legitimate use in this caching context across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/logger | AI (phantom-deps): Same-org sibling dep; declared in dependencies, phantom-dep heuristic fires but is a stable false positive for this monorepo package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 6 / 2 | |
| 4.8.12 | 6 / 2 | |
| 4.8.11 | 6 / 2 | |
| 4.8.9 | 6 / 2 | |
| 4.8.3 | 6 / 2 | |
| 4.8.2 | 6 / 2 | |
| 4.7.2 | 6 / 2 | |
| 4.6.2 | 6 / 2 | |
| 4.6.0 | 6 / 2 | |
| 4.4.0 | 6 / 2 | |
| 4.3.6 | 6 / 3 | |
| 4.3.5 | 6 / 3 | |
| 4.3.3 | 6 / 3 | |
| 4.3.2 | 6 / 3 | |
| 4.3.1 | 6 / 3 | |
| 4.1.3 | 6 / 3 | |
| 4.1.1 | 6 / 3 | |
| 4.0.2 | 6 / 3 | |
| 4.0.1 | 6 / 3 | |
| 4.0.0 | 6 / 3 |
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.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.
v4.8.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.7.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.6.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.6.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.
v4.4.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.
v4.3.6
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.3.5
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.3.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.
v4.3.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.3.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.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.
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.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.