@forwardimpact/libsyntheticprose

LLM-based prose and pathway generation for synthetic data

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dickolsson

Keywords

syntheticprosellmagenteval

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New dep is same-org @forwardimpact scope, consistent with package purpose and publisher track record.	ai	2026/05/27
phantom-deps	phantom-dep:@forwardimpact/libtelemetry	AI (phantom-deps): Same-org scoped dep; declared as a runtime dependency, phantom-dep heuristic is a false positive here.	ai	2026/05/07
provenance	no-provenance	AI (provenance): Consistent across all @forwardimpact packages in this monorepo; not a meaningful risk signal here.	ai	2026/05/04
phantom-deps	phantom-dep:ajv	AI (phantom-deps): ajv declared as direct dep for schema validation; phantom-dep heuristic fires due to indirect/config usage pattern.	ai	2026/04/30
phantom-deps	phantom-dep:yaml	AI (phantom-deps): yaml declared as direct dep; phantom-dep heuristic fires due to indirect/config usage pattern.	ai	2026/04/30
phantom-deps	phantom-dep:ajv-formats	AI (phantom-deps): ajv-formats declared as direct dep alongside ajv; phantom-dep heuristic fires due to indirect/config usage pattern.	ai	2026/04/30

Versions (showing 28 of 28)

Version	Deps	Published
0.1.32	7 / 1	2026-05-31
0.1.31	7 / 0	2026-05-28
0.1.30	7 / 0	2026-05-25
0.1.29	7 / 0	2026-05-23
0.1.28	7 / 0	2026-05-23
0.1.27	7 / 0	2026-05-19
0.1.26	6 / 0	2026-05-17
0.1.24	6 / 0	2026-05-08
0.1.23	6 / 0	2026-05-07
0.1.22	6 / 0	2026-05-05
0.1.21	6 / 0	2026-05-05
0.1.20	6 / 0	2026-05-03
0.1.19	6 / 0	2026-05-01
0.1.18	6 / 0	2026-05-01
0.1.17	6 / 0	2026-04-28
0.1.16	6 / 0	2026-04-27
0.1.15	6 / 0	2026-04-26
0.1.14	6 / 0	2026-04-22
0.1.13	6 / 0	2026-04-21
0.1.12	6 / 0	2026-04-17
0.1.11	6 / 0	2026-04-13
0.1.10	6 / 0	2026-04-11
0.1.8	6 / 0	2026-04-03
0.1.5	6 / 0	2026-04-01
0.1.4	6 / 0	2026-03-30
0.1.3	6 / 0	2026-03-28
0.1.2	6 / 0	2026-03-27
0.1.1	6 / 0	2026-03-26

v0.1.32

1 finding

INFO No provenance attestation provenance

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

v0.1.31

1 finding

INFO No provenance attestation provenance

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

v0.1.30

1 finding

INFO No provenance attestation provenance

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

v0.1.29

1 finding

INFO No provenance attestation provenance

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

v0.1.28

1 finding

INFO No provenance attestation provenance

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

v0.1.27

1 finding

INFO No provenance attestation provenance

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

v0.1.26

1 finding

INFO No provenance attestation provenance

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

v0.1.24

1 finding

INFO No provenance attestation provenance

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

v0.1.23

1 finding

INFO No provenance attestation provenance

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

v0.1.22

1 finding

INFO No provenance attestation provenance

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

v0.1.21

1 finding

INFO No provenance attestation provenance

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

v0.1.20

1 finding

INFO No provenance attestation provenance

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

v0.1.19

1 finding

INFO No provenance attestation provenance

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

v0.1.18

1 finding

INFO No provenance attestation provenance

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

v0.1.17

1 finding

INFO No provenance attestation provenance

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

v0.1.16

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.1.15

1 finding

INFO No provenance attestation provenance

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

v0.1.14

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.1.13

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.1.12

1 finding

INFO No provenance attestation provenance

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

v0.1.11

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.1.10

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.1.8

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.1.5

1 finding

INFO No provenance attestation provenance

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

v0.1.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.1.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.1.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.

v0.1.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.