← Home

@framtidtechas/cli

CLI for Framtid CMS — bootstrap, migrate, seed, doctor, schema, init

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

framtid

Keywords

cmsframtidclisupabasemigration

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern rapid-publish AI (publish-pattern): High-frequency monorepo releases; 137 versions with consistent rapid publish cadence, not indicative of malicious activity. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped CMS CLI package; Levenshtein match to 'joi' is coincidental, not impersonation. ai
phantom-deps phantom-dep:@framtidtechas/db-core AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo packages. ai

Versions (showing 9 of 9)

Version Deps Published
1.47.25 4 / 5
1.47.24 4 / 5
1.47.23 4 / 5
1.42.39 4 / 5
1.42.37 4 / 5
1.42.24 4 / 5
1.42.22 4 / 5
1.42.8 4 / 5
1.5.6 4 / 5

v1.47.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.47.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.47.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.