@bpinternal/const UNLICENSED 97 versions

@bpinternal/const

npm

Shared constants for Skynet billing refactor (vendored copy of upstream packages/const)

97

Versions

UNLICENSED

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

allardymichael.massonfranklevasseurslvnperronxavierhamelbotpress-cloud-ops

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): zod is a widely-used, well-vetted validation library; no malicious signal.	ai	2026/05/04
license	uncommon-license:UNLICENSED	AI (license): Intentionally UNLICENSED internal vendored package per description; stable across versions.	ai	2026/05/04
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped @bpinternal package; name collision with 'cors' is coincidental, not impersonation.	ai	2026/04/29

Versions (showing 97 of 97)

Version	Deps	Published
0.29.0	1 / 1	2026-07-27
0.28.0	1 / 1	2026-06-09
0.27.0	1 / 1	2026-06-08
0.26.0	1 / 1	2026-06-05
0.25.0	1 / 1	2026-06-03
0.24.0	1 / 1	2026-05-13
0.23.0	1 / 1	2026-05-12
0.22.0	1 / 1	2026-05-11
0.21.0	1 / 1	2026-05-08
0.20.0	1 / 1	2026-05-06
0.19.0	1 / 1	2026-05-06
0.18.0	1 / 1	2026-05-04
0.17.0	1 / 1	2026-05-04
0.16.0	1 / 1	2026-05-04
0.15.0	1 / 1	2026-04-29
0.14.1	1 / 1	2026-04-27
0.14.0	1 / 1	2026-04-24
0.13.0	1 / 1	2026-04-23
0.12.0	1 / 1	2026-04-22
0.11.0	1 / 1	2026-04-21
0.10.0	1 / 1	2026-04-16
0.9.0	1 / 1	2026-04-09
0.8.0	1 / 1	2026-04-08
0.7.0	1 / 1	2026-04-06
0.5.2	1 / 1	2026-03-25
0.5.1	1 / 1	2026-03-25
0.5.0	1 / 1	2026-03-24
0.4.3	1 / 1	2026-03-24
0.4.2	1 / 1	2026-01-28
0.4.1	1 / 1	2025-12-04
0.3.9	0 / 1	2025-11-24
0.3.8	0 / 1	2025-11-24
0.3.7	0 / 1	2025-11-03
0.3.6	0 / 1	2025-10-01
0.3.5	0 / 1	2025-09-19
0.3.4	0 / 1	2025-08-14
0.3.3	0 / 1	2025-07-29
0.3.2	0 / 1	2025-07-09
0.3.1	0 / 1	2025-07-09
0.3.0	0 / 1	2025-07-08
0.2.3	0 / 4	2025-07-18
0.2.2	0 / 5	2025-05-27
0.2.1	0 / 5	2025-05-08
0.2.0	0 / 5	2025-04-23
0.1.2	0 / 5	2025-04-11
0.1.1	0 / 5	2025-04-01
0.1.0	0 / 5	2025-02-17
0.0.50	0 / 5	2025-02-10
0.0.49	0 / 5	2025-02-04
0.0.48	0 / 5	2025-01-03
0.0.47	0 / 5	2024-12-24
0.0.46	0 / 5	2024-12-04
0.0.45	0 / 5	2024-12-03
0.0.44	0 / 5	2024-11-15
0.0.43	0 / 5	2024-10-16
0.0.42	0 / 5	2024-09-26
0.0.41	0 / 5	2024-09-25
0.0.40	0 / 5	2024-09-05
0.0.39	0 / 5	2024-08-19
0.0.38	0 / 5	2024-06-13
0.0.37	0 / 5	2024-06-10
0.0.36	0 / 5	2024-05-06
0.0.35	0 / 5	2024-05-01
0.0.34	0 / 5	2024-04-17
0.0.33	0 / 5	2024-04-01
0.0.32	0 / 5	2024-03-22
0.0.31	0 / 5	2024-03-18
0.0.30	1 / 4	2024-02-28
0.0.29	1 / 4	2024-02-18
0.0.28	1 / 4	2024-02-13
0.0.27	1 / 4	2024-02-12
0.0.26	1 / 4	2024-01-26
0.0.25	1 / 4	2024-01-24
0.0.24	1 / 4	2024-01-19
0.0.23	1 / 4	2024-01-19
0.0.22	1 / 4	2023-12-21
0.0.21	1 / 4	2023-12-12
0.0.20	1 / 4	2023-12-11
0.0.19	1 / 4	2023-12-08
0.0.18	1 / 4	2023-12-07
0.0.17	1 / 4	2023-12-06
0.0.16	1 / 4	2023-12-06
0.0.15	1 / 4	2023-12-05
0.0.14	1 / 4	2023-11-21
0.0.13	1 / 4	2023-11-17
0.0.12	1 / 4	2023-10-30
0.0.11	1 / 4	2023-10-26
0.0.10	1 / 4	2023-10-24
0.0.9	1 / 4	2023-10-24
0.0.8	1 / 4	2023-10-06
0.0.7	1 / 4	2023-10-04
0.0.6	1 / 4	2023-09-27
0.0.5	1 / 4	2023-09-20
0.0.4	1 / 4	2023-09-20
0.0.3	1 / 4	2023-09-20
0.0.2	1 / 4	2023-09-19
0.0.1	1 / 4	2023-09-18

v0.29.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.50

1 finding

LOW No provenance attestation provenance

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

v0.0.49

1 finding

LOW No provenance attestation provenance

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

v0.0.48

1 finding

LOW No provenance attestation provenance

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

v0.0.47

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.34

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.0.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.0.15

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.0.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.0.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.0.12

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.0.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.0.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.0.9

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.0.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.0.7

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.0.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.0.5

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