@braintrust/core No license 51 versions

@braintrust/core

npm Repository Homepage

51

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

clutchskibraintrust

Keywords

ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@mapbox/node-pre-gyp	AI (phantom-deps): Used in install script config, not imported; expected for node-pre-gyp.	ai	2026/07/19
install-scripts	install-script:install	AI (install-scripts): Compiles native addon via cargo-cp-artifact; documented build, no remote fetch.	ai	2026/07/19
npm-metadata	bundled-binaries	AI (npm-metadata): index.node is the built Neon addon, the package's stated purpose.	ai	2026/07/19
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped official Braintrust package, unrelated to 'cors'; stable FP.	ai	2026/07/18

Versions (showing 51 of 60)

View all versions

Version	Deps	Published
0.0.95	2 / 7	2025-08-26
0.0.94	3 / 7	2025-08-22
0.0.93	3 / 7	2025-08-07
0.0.92	3 / 7	2025-08-05
0.0.91	3 / 7	2025-07-25
0.0.57	3 / 7	2024-09-26
0.0.56	3 / 7	2024-09-24
0.0.55	3 / 7	2024-09-19
0.0.54	3 / 7	2024-09-04
0.0.52	3 / 7	2024-08-26
0.0.51	3 / 7	2024-08-07
0.0.50	3 / 7	2024-08-07
0.0.49	3 / 7	2024-08-02
0.0.48	3 / 7	2024-08-01
0.0.47	3 / 7	2024-07-23
0.0.46	3 / 7	2024-07-17
0.0.45	3 / 7	2024-07-09
0.0.44	3 / 5	2024-07-05
0.0.43	3 / 5	2024-07-01
0.0.42	3 / 5	2024-06-29
0.0.41	3 / 5	2024-06-25
0.0.40	3 / 5	2024-06-18
0.0.39	3 / 5	2024-06-13
0.0.38	3 / 5	2024-06-12
0.0.37	3 / 5	2024-05-28
0.0.36	3 / 5	2024-05-24
0.0.35	3 / 5	2024-05-18
0.0.34	3 / 4	2024-04-26
0.0.33	3 / 4	2024-04-25
0.0.32	2 / 3	2024-04-24
0.0.31	2 / 3	2024-04-17
0.0.30	2 / 3	2024-04-09
0.0.28	2 / 3	2024-04-02
0.0.27	2 / 3	2024-03-26
0.0.26	2 / 3	2024-03-17
0.0.25	2 / 3	2024-03-17
0.0.24	2 / 3	2024-03-17
0.0.23	2 / 3	2024-03-17
0.0.22	2 / 3	2024-03-14
0.0.21	2 / 3	2024-03-07
0.0.20	2 / 3	2024-03-04
0.0.19	2 / 3	2024-02-25
0.0.18	2 / 3	2024-02-23
0.0.17	2 / 3	2024-02-20
0.0.16	2 / 3	2024-02-15
0.0.15	0 / 3	2024-02-09
0.0.14	0 / 3	2024-02-04
0.0.13	0 / 3	2024-01-26
0.0.12	0 / 3	2024-01-23
0.0.11	0 / 3	2024-01-16
0.0.10	0 / 3	2024-01-13

v0.0.95

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

1 finding

LOW No provenance attestation provenance

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

v0.0.93

1 finding

LOW No provenance attestation provenance

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

v0.0.92

1 finding

LOW No provenance attestation provenance

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

v0.0.91

1 finding

LOW No provenance attestation provenance

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

v0.0.57

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@braintrust/core' is 1 edit(s) away from popular package 'cors'.

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

1 finding

LOW No provenance attestation provenance

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

v0.0.45

1 finding

LOW No provenance attestation provenance

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

v0.0.44

1 finding

LOW No provenance attestation provenance

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

v0.0.43

1 finding

LOW No provenance attestation provenance

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

v0.0.42

1 finding

LOW No provenance attestation provenance

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

v0.0.41

1 finding

LOW No provenance attestation provenance

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

v0.0.40

1 finding

LOW No provenance attestation provenance

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

v0.0.39

1 finding

LOW No provenance attestation provenance

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

v0.0.38

1 finding

LOW No provenance attestation provenance

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

v0.0.37

1 finding

LOW No provenance attestation provenance

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

v0.0.36

1 finding

LOW No provenance attestation provenance

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

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

1 finding

LOW No provenance attestation provenance

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

v0.0.25

1 finding

LOW No provenance attestation provenance

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

v0.0.24

1 finding

LOW No provenance attestation provenance

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

v0.0.23

1 finding

LOW No provenance attestation provenance

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

v0.0.22

1 finding

LOW No provenance attestation provenance

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

v0.0.21

1 finding

LOW No provenance attestation provenance

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

v0.0.20

1 finding

LOW No provenance attestation provenance

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

v0.0.19

1 finding

LOW No provenance attestation provenance

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

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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