@framework-m/desk Apache-2.0 17 versions

@framework-m/desk

npm Repository

Business components, hooks, views, and providers for Framework M applications

17

Versions

Apache-2.0

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

revant

Keywords

framework-mrefinedata-providerauth-providerlive-providerdeskerp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@framework-m/ui	AI (phantom-deps): Same-org sibling dep; declared in both dependencies and devDependencies, heuristic false positive.	ai	2026/05/15
typosquat	typosquat.levenshtein:jest	AI (typosquat): Scoped ERP framework package; Levenshtein match to 'jest' is coincidental, not impersonation.	ai	2026/05/15

Versions (showing 17 of 17)

Version	Deps	Published
0.12.0	2 / 39	2026-06-02
0.11.0	2 / 39	2026-05-29
0.10.1	2 / 39	2026-05-26
0.10.0	2 / 39	2026-05-17
0.9.1	2 / 39	2026-05-06
0.9.0	2 / 39	2026-04-29
0.8.0	2 / 34	2026-04-20
0.7.0	2 / 34	2026-04-06
0.6.2	2 / 29	2026-04-05
0.6.1	2 / 29	2026-04-04
0.6.0	2 / 29	2026-04-04
0.5.1	2 / 29	2026-03-30
0.5.0	2 / 29	2026-03-30
0.4.6	1 / 25	2026-03-26
0.4.4	1 / 25	2026-03-25
0.4.3	1 / 25	2026-03-23
0.4.2	1 / 25	2026-03-23

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.