@uxf/cms
UXF Cms
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@redux-devtools/extension | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:swr | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:redux | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@uxf/core | AI (phantom-deps): Same-org scoped dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@uxf/form | AI (phantom-deps): Same-org scoped dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:es6-error | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@uxf/router | AI (phantom-deps): Same-org scoped dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:axios-hooks | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@uxf/core-react | AI (phantom-deps): Same-org scoped dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @uxf org package with 621 versions; Levenshtein match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @uxf org package with 621 versions; Levenshtein match to 'cors' is a false positive. | ai |
Versions (showing 100 of 208)
| Version | Deps | Published |
|---|---|---|
| 11.67.0 | 20 / 7 | |
| 11.66.1 | 20 / 7 | |
| 11.66.0 | 20 / 7 | |
| 11.65.0 | 20 / 7 | |
| 11.64.5 | 20 / 7 | |
| 11.64.4 | 20 / 7 | |
| 11.63.1 | 20 / 7 | |
| 11.61.0 | 20 / 7 | |
| 11.60.4 | 20 / 7 | |
| 11.60.3 | 20 / 7 | |
| 11.60.2 | 20 / 7 | |
| 11.60.1 | 20 / 7 | |
| 11.59.1 | 20 / 7 | |
| 11.59.0 | 20 / 7 | |
| 11.58.1 | 20 / 7 | |
| 11.58.0 | 20 / 7 | |
| 11.57.0 | 20 / 7 | |
| 11.56.1 | 20 / 7 | |
| 11.56.0 | 20 / 7 | |
| 11.55.0 | 20 / 7 | |
| 11.54.0 | 20 / 7 | |
| 11.53.2 | 20 / 7 | |
| 11.53.1 | 20 / 7 | |
| 11.53.0 | 20 / 7 | |
| 11.52.3 | 20 / 7 | |
| 11.52.2 | 20 / 7 | |
| 11.52.1 | 20 / 7 | |
| 11.52.0 | 20 / 7 | |
| 11.51.2 | 20 / 7 | |
| 11.51.1 | 20 / 7 | |
| 11.51.0 | 20 / 7 | |
| 11.50.0 | 20 / 7 | |
| 11.49.4 | 20 / 7 | |
| 11.49.2 | 20 / 7 | |
| 11.49.1 | 20 / 7 | |
| 11.49.0 | 20 / 7 | |
| 11.48.4 | 20 / 7 | |
| 11.48.3 | 20 / 7 | |
| 11.48.2 | 20 / 7 | |
| 11.48.1 | 20 / 7 | |
| 11.48.0 | 20 / 7 | |
| 11.47.2 | 20 / 7 | |
| 11.47.1 | 20 / 7 | |
| 11.47.0 | 20 / 7 | |
| 11.46.0 | 20 / 7 | |
| 11.45.1 | 20 / 7 | |
| 11.45.0 | 20 / 7 | |
| 11.44.0 | 20 / 7 | |
| 11.43.0 | 20 / 7 | |
| 11.42.1 | 20 / 7 | |
| 11.42.0 | 20 / 7 | |
| 11.41.4 | 20 / 7 | |
| 11.41.1 | 20 / 7 | |
| 11.41.0 | 20 / 7 | |
| 11.40.0 | 20 / 7 | |
| 11.39.0 | 20 / 7 | |
| 11.38.3 | 20 / 7 | |
| 11.38.2 | 20 / 7 | |
| 11.38.1 | 20 / 7 | |
| 11.38.0 | 20 / 7 | |
| 11.37.0 | 20 / 7 | |
| 11.36.0 | 20 / 7 | |
| 11.35.0 | 20 / 7 | |
| 11.34.1 | 20 / 7 | |
| 11.34.0 | 20 / 7 | |
| 11.33.2 | 20 / 7 | |
| 11.33.1 | 20 / 7 | |
| 11.33.0 | 20 / 7 | |
| 11.32.0 | 20 / 7 | |
| 11.31.2 | 20 / 7 | |
| 11.31.1 | 20 / 7 | |
| 11.31.0 | 20 / 7 | |
| 11.30.1 | 20 / 7 | |
| 11.30.0 | 20 / 7 | |
| 11.29.0 | 20 / 7 | |
| 11.28.5 | 20 / 7 | |
| 11.28.4 | 20 / 7 | |
| 11.28.2 | 20 / 7 | |
| 11.28.1 | 20 / 7 | |
| 11.28.0 | 20 / 7 | |
| 11.27.1 | 20 / 7 | |
| 11.27.0 | 20 / 7 | |
| 11.26.0 | 20 / 7 | |
| 11.25.1 | 20 / 7 | |
| 11.25.0 | 20 / 7 | |
| 11.24.2 | 20 / 7 | |
| 11.24.1 | 20 / 7 | |
| 11.24.0 | 20 / 7 | |
| 11.23.2 | 20 / 7 | |
| 11.23.0 | 20 / 7 | |
| 11.22.1 | 20 / 7 | |
| 11.22.0 | 20 / 7 | |
| 11.21.5 | 20 / 7 | |
| 11.21.4 | 20 / 7 | |
| 11.21.3 | 20 / 7 | |
| 11.21.2 | 20 / 7 | |
| 11.21.1 | 20 / 7 | |
| 11.21.0 | 20 / 7 | |
| 11.20.0 | 20 / 7 | |
| 11.19.3 | 19 / 7 |
v11.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.60.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.60.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.53.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.53.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.52.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.52.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.49.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.48.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.