@pi-r/gcp MIT 75 versions

@pi-r/gcp

npm Repository Homepage

Google (GCP) cloud functions for E-mc.

75

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

anpham6

Keywords

squarede-mc

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped package @pi-r/gcp; Levenshtein match to 'got' is coincidental, not a typosquat.	ai	2026/04/28
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped package @pi-r/gcp; Levenshtein match to 'yup' is coincidental, not a typosquat.	ai	2026/04/28
semgrep	semgrep:dynamic-require	AI (semgrep): Lazy-loads @google-cloud/spanner by literal string constant; not truly dynamic/arbitrary.	ai	2026/04/28
phantom-deps	phantom-dep:@e-mc/module	AI (phantom-deps): Referenced in config files per finding; stable false positive for this package.	ai	2026/04/28

Versions (showing 75 of 75)

Version	Deps	Published
0.12.3	5 / 0	2026-07-05
0.12.2	5 / 0	2026-06-17
0.12.1	5 / 0	2026-05-10
0.12.0	5 / 0	2026-04-29
0.11.3	5 / 0	2026-04-25
0.11.2	5 / 0	2026-03-20
0.11.1	5 / 0	2026-01-07
0.11.0	5 / 0	2025-10-19
0.10.5	5 / 0	2026-07-12
0.10.4	5 / 0	2026-04-25
0.10.3	5 / 0	2025-09-16
0.10.2	5 / 0	2025-08-09
0.10.1	5 / 0	2025-05-14
0.10.0	5 / 0	2025-04-29
0.9.6	5 / 0	2026-07-12
0.9.5	5 / 0	2026-04-25
0.9.4	5 / 0	2025-04-01
0.9.3	5 / 0	2025-03-29
0.9.2	5 / 0	2025-03-06
0.9.1	5 / 0	2025-02-07
0.9.0	5 / 0	2024-12-08
0.8.6	5 / 0	2026-07-12
0.8.5	5 / 0	2026-04-25
0.8.4	5 / 0	2025-03-29
0.8.3	5 / 0	2024-10-12
0.8.2	5 / 0	2024-09-21
0.8.1	5 / 0	2024-08-24
0.8.0	5 / 0	2024-08-07
0.7.7	5 / 0	2026-07-05
0.7.6	5 / 0	2026-04-25
0.7.5	5 / 0	2025-03-29
0.7.4	5 / 0	2024-10-08
0.7.3	5 / 0	2024-07-24
0.7.2	5 / 0	2024-07-01
0.7.1	5 / 0	2024-05-27
0.7.0	5 / 0	2024-04-30
0.6.11	5 / 0	2026-07-05
0.6.10	5 / 0	2026-04-25
0.6.9	5 / 0	2025-03-29
0.6.8	5 / 0	2024-07-18
0.6.7	5 / 0	2024-05-01
0.6.6	5 / 0	2024-04-03
0.6.5	5 / 0	2024-03-07
0.6.3	5 / 0	2024-01-31
0.6.2	5 / 0	2024-01-27
0.6.1	5 / 0	2024-01-08
0.6.0	5 / 0	2023-12-24
0.5.7	5 / 0	2026-07-05
0.5.6	5 / 0	2025-03-29
0.5.5	5 / 0	2024-07-18
0.5.4	5 / 0	2024-05-01
0.5.3	5 / 0	2024-05-01
0.5.2	5 / 0	2024-03-05
0.5.0	5 / 0	2023-12-08
0.3.8	5 / 0	2026-07-05
0.3.7	5 / 0	2025-03-29
0.3.6	5 / 0	2025-03-29
0.3.5	5 / 0	2024-07-18
0.3.4	5 / 0	2024-05-01
0.3.3	5 / 0	2024-04-02
0.3.2	5 / 0	2024-03-05
0.3.1	5 / 0	2023-12-04
0.3.0	5 / 0	2023-08-07
0.2.14	5 / 0	2026-07-05
0.2.13	5 / 0	2025-03-29
0.2.12	5 / 0	2024-07-18
0.2.11	5 / 0	2024-05-01
0.2.10	5 / 0	2024-05-01
0.2.9	5 / 0	2024-04-02
0.2.8	5 / 0	2024-03-05
0.2.2	5 / 0	2023-05-18
0.2.1	5 / 0	2023-04-29
0.2.0	5 / 0	2023-04-18
0.1.0	5 / 0	2023-04-10
0.0.1	5 / 0	2023-03-17

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.10.5

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.4

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

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

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.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.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.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.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.3.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.3.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.3.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.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

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