@factoryfour/client MIT 51 versions

@factoryfour/client

npm

User-friendly JS client for the FactoryFour API

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sebastian.vecchiozwarrenjluttrellluis.isasixom-sreserviceuserjfbrennanmatthewzhaocc1jmiller-xombisurgixometrymhalbexom-mtangabrielpasquantoniojoacogaonaaarontropycamnkimxomgc3mike.kmiecjoshpoolexometrysshilal1nicoevergaraaaronivanamaroalanzicriley-xomlhendrixmattleibelmnlernerses13alexjmathewscorychof4-traviscmoetellavipparlavsp20jthai006evrim.persembe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@factoryfour/frame-client	AI (dependencies): Same-org first-party sibling package, not a third-party supply-chain risk.	ai	2026/07/27
phantom-deps	phantom-dep:@factoryfour/frame-client	AI (phantom-deps): Same-org dep, likely used indirectly; heuristic false positive.	ai	2026/07/27
phantom-deps	phantom-dep:@types/luxon	AI (phantom-deps): @types/luxon is a TypeScript type package; not directly imported but used by convention — stable false positive for this package.	ai	2026/04/29

Versions (showing 51 of 73)

View all versions

Version	Deps	Published
1.12.6	8 / 9	2023-07-14
1.12.5	8 / 10	2022-10-19
1.12.4	8 / 10	2022-05-06
1.12.3	8 / 10	2022-03-31
1.12.2	8 / 10	2022-03-30
1.12.1	8 / 10	2022-03-30
1.12.0	8 / 10	2022-03-29
1.11.0	8 / 10	2022-02-25
1.10.4	8 / 10	2021-10-19
1.10.3	8 / 10	2021-10-15
1.10.2	8 / 10	2021-10-14
1.10.1	8 / 10	2021-09-27
1.10.0	8 / 10	2021-09-20
1.9.3	8 / 10	2021-08-31
1.9.2	8 / 10	2021-08-30
1.9.1	8 / 10	2021-07-01
1.9.0	8 / 10	2021-06-07
1.8.3	8 / 10	2021-05-12
1.8.2	8 / 10	2021-05-03
1.8.1	8 / 10	2021-04-16
1.7.4	8 / 10	2021-04-05
1.7.3	7 / 11	2021-04-05
1.7.2	7 / 11	2021-03-24
1.7.1	7 / 11	2021-03-12
1.7.0	7 / 11	2021-03-11
1.6.7	4 / 10	2021-01-05
1.6.6	4 / 10	2020-12-15
1.6.5	4 / 10	2020-10-29
1.6.4	4 / 10	2020-09-18
1.6.3	4 / 10	2020-09-18
1.6.2	4 / 10	2020-08-06
1.6.1	4 / 10	2020-08-06
1.6.0	4 / 10	2020-05-30
1.5.19	4 / 10	2020-05-28
1.5.18	4 / 10	2020-05-19
1.5.17	4 / 10	2020-05-06
1.5.16	4 / 10	2020-05-03
1.5.15	4 / 10	2020-05-03
1.5.14	4 / 10	2020-05-03
1.5.13	4 / 10	2020-04-06
1.5.12	4 / 10	2020-04-03
1.5.11	4 / 10	2020-04-03
1.5.10	5 / 10	2020-03-30
1.5.9	5 / 10	2020-03-25
1.5.8	5 / 10	2020-03-25
1.5.7	5 / 10	2020-03-25
1.5.6	5 / 10	2020-03-19
1.5.5	5 / 10	2020-03-16
1.5.4	5 / 10	2020-03-10
1.5.3	5 / 10	2020-03-09
1.5.2	5 / 10	2020-03-03

v1.12.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: lhendrix → corycho (on 2022-10-19, known maintainer) provenance

This version was published by a different npm account (corycho) than the most recent previously approved version (lhendrix) on 2022-10-19, but corycho is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.12.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: lhendrix → alexjmathews (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (lhendrix) on 2022-05-06, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.12.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: alexjmathews → lhendrix (on 2022-03-31, known maintainer) provenance

This version was published by a different npm account (lhendrix) than the most recent previously approved version (alexjmathews) on 2022-03-31, but lhendrix is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.12.2

1 finding

LOW No provenance attestation provenance

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

v1.12.1

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.4

1 finding

LOW No provenance attestation provenance

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

v1.10.3

1 finding

LOW No provenance attestation provenance

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

v1.10.2

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chrmcg → alexjmathews (on 2021-08-31, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (chrmcg) on 2021-08-31, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.9.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chrmcg → alexjmathews (on 2021-08-30, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (chrmcg) on 2021-08-30, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.3

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.7.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.7

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chrmcg → alexjmathews (on 2021-01-05, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (chrmcg) on 2021-01-05, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.19

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: alexjmathews → chrmcg (on 2020-05-28, known maintainer) provenance

This version was published by a different npm account (chrmcg) than the most recent previously approved version (alexjmathews) on 2020-05-28, but chrmcg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.18

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: alexjmathews → chrmcg (on 2020-05-19, known maintainer) provenance

This version was published by a different npm account (chrmcg) than the most recent previously approved version (alexjmathews) on 2020-05-19, but chrmcg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.17

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chrmcg → alexjmathews (on 2020-05-06, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (chrmcg) on 2020-05-06, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.16

1 finding

LOW No provenance attestation provenance

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

v1.5.15

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: alexjmathews → chrmcg (on 2020-05-03, known maintainer) provenance

This version was published by a different npm account (chrmcg) than the most recent previously approved version (alexjmathews) on 2020-05-03, but chrmcg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.14

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: alexjmathews → chrmcg (on 2020-05-03, known maintainer) provenance

This version was published by a different npm account (chrmcg) than the most recent previously approved version (alexjmathews) on 2020-05-03, but chrmcg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.13

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chrmcg → alexjmathews (on 2020-04-06, known maintainer) provenance

This version was published by a different npm account (alexjmathews) than the most recent previously approved version (chrmcg) on 2020-04-06, but alexjmathews is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.12

1 finding

LOW No provenance attestation provenance

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

v1.5.11

1 finding

LOW No provenance attestation provenance

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

v1.5.10

1 finding

LOW No provenance attestation provenance

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

v1.5.9

1 finding

LOW No provenance attestation provenance

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

v1.5.8

1 finding

LOW No provenance attestation provenance

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

v1.5.7

1 finding

LOW No provenance attestation provenance

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

v1.5.6

1 finding

LOW No provenance attestation provenance

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

v1.5.5

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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