@c-rex/templates No license 35 versions

@c-rex/templates

npm

35

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

Maintainers

mwiedenmaierperiottocosta

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@c-rex/utils	AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo.	ai	2026/05/11
npm-metadata	no-description	AI (npm-metadata): Common in internal monorepo packages; no malware indicator.	ai	2026/05/11
phantom-deps	phantom-dep:@c-rex/services	AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo.	ai	2026/05/11
phantom-deps	phantom-dep:cheerio	AI (phantom-deps): Internal template package; deps declared for bundling/type resolution, not direct imports.	ai	2026/05/05
bogus-package	bogus-package	AI (bogus-package): Internal monorepo package; no public description/repo/keywords is expected for private org packages.	ai	2026/05/05
phantom-deps	phantom-dep:sonner	AI (phantom-deps): Re-exported from @c-rex packages; legitimate transitive dependency pattern.	ai	2026/05/05
phantom-deps	phantom-dep:i18next	AI (phantom-deps): Re-exported from @c-rex packages; legitimate transitive dependency pattern.	ai	2026/05/05
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Re-exported from @c-rex packages; legitimate transitive dependency pattern.	ai	2026/05/05
phantom-deps	phantom-dep:zustand	AI (phantom-deps): Re-exported from @c-rex packages; legitimate transitive dependency pattern.	ai	2026/05/05
phantom-deps	phantom-dep:react-i18next	AI (phantom-deps): Re-exported from @c-rex packages; legitimate transitive dependency pattern.	ai	2026/05/05

Versions (showing 35 of 35)

Version	Deps	Published
0.1.30	19 / 8	2026-03-06
0.1.29	16 / 8	2026-02-22
0.1.28	16 / 8	2026-02-16
0.1.27	16 / 8	2026-01-07
0.1.26	16 / 8	2025-12-03
0.1.25	16 / 8	2025-12-03
0.1.24	16 / 8	2025-12-03
0.1.23	16 / 8	2025-12-03
0.1.22	16 / 8	2025-12-03
0.1.21	16 / 8	2025-11-21
0.1.20	16 / 8	2025-11-10
0.1.19	16 / 8	2025-11-08
0.1.18	16 / 8	2025-11-01
0.1.17	16 / 8	2025-10-21
0.1.16	16 / 8	2025-10-06
0.1.15	16 / 8	2025-10-02
0.1.14	15 / 8	2025-09-12
0.1.13	15 / 8	2025-09-12
0.1.12	15 / 8	2025-09-11
0.1.11	15 / 8	2025-09-01
0.1.10	15 / 8	2025-08-19
0.1.9	15 / 8	2025-08-04
0.1.8	15 / 8	2025-07-26
0.1.7	15 / 8	2025-07-22
0.1.6	15 / 8	2025-07-15
0.1.5	15 / 8	2025-07-15
0.1.4	15 / 8	2025-07-15
0.1.3	14 / 8	2025-06-19
0.1.2	13 / 8	2025-06-03
0.1.1	13 / 8	2025-05-27
0.1.0	13 / 8	2025-05-27
0.0.12	8 / 8	2025-05-10
0.0.11	8 / 8	2025-04-29
0.0.10	8 / 8	2025-04-29
0.0.9	8 / 9	2025-04-29

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.3

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