@aphexcms/cms-core
Aphex CMS Core - A Sanity-style CMS with ports and adapters architecture
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a dev/CLI tool referenced in config, not a runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:s3mini | AI (phantom-deps): s3mini referenced in config files only, not directly imported; consistent with optional storage adapter pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/svelte | AI (phantom-deps): Svelte component library likely imported via Svelte-specific resolution paths not detected by static analysis. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/helpers | AI (phantom-deps): Same as @dnd-kit/svelte; Svelte resolution pattern causes false positive. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 9.2.0 | 18 / 22 | |
| 9.1.0 | 18 / 22 | |
| 9.0.0 | 13 / 22 | |
| 8.1.0 | 14 / 22 | |
| 8.0.0 | 14 / 22 | |
| 7.0.0 | 14 / 22 | |
| 6.0.0 | 14 / 22 | |
| 5.1.0 | 14 / 22 | |
| 5.0.5 | 14 / 22 | |
| 5.0.3 | 14 / 22 | |
| 5.0.1 | 14 / 22 | |
| 5.0.0 | 14 / 22 | |
| 4.0.0 | 12 / 22 | |
| 3.0.0 | 12 / 22 | |
| 2.1.2 | 12 / 22 | |
| 2.1.1 | 12 / 22 | |
| 2.1.0 | 12 / 22 | |
| 2.0.11 | 12 / 22 | |
| 2.0.10 | 12 / 22 | |
| 2.0.9 | 11 / 22 | |
| 2.0.8 | 11 / 22 | |
| 2.0.7 | 11 / 22 | |
| 2.0.6 | 11 / 22 | |
| 1.0.0 | 11 / 22 | |
| 0.1.15 | 6 / 22 | |
| 0.1.12 | 2 / 22 | |
| 0.1.11 | 2 / 22 | |
| 0.1.10 | 2 / 22 | |
| 0.1.9 | 2 / 22 | |
| 0.1.8 | 2 / 22 |
v9.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.