@cntrl-site/sdk No license 28 versions

@cntrl-site/sdk

npm Repository Homepage

28

Versions

—

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

Maintainers

paula.uliarsenbatyuchoksergokikotkustovtimurvnukov

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Established SDK package with 230 versions; sparse README/keywords are cosmetic, not indicative of spam.	ai	2026/05/23
phantom-deps	phantom-dep:@splidejs/react-splide	AI (phantom-deps): Runtime dep used by consumers; stable false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:styled-jsx	AI (phantom-deps): Framework-scoped CSS-in-JS package; loaded by convention, not directly imported.	ai	2026/05/13
phantom-deps	phantom-dep:ts-node	AI (phantom-deps): ts-node is a runtime CLI dependency used in build/config context; stable false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:@types/isomorphic-fetch	AI (phantom-deps): Type-only package; stable false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:@types/ua-parser-js	AI (phantom-deps): Type-only package; stable false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:@types/ejs	AI (phantom-deps): Type-only package loaded by convention; not directly imported in source.	ai	2026/05/13

Versions (showing 28 of 28)

Version	Deps	Published
1.27.1	14 / 11	2026-05-13
1.27.0	14 / 11	2026-05-13
1.26.5	14 / 11	2026-05-13
1.26.4	14 / 11	2026-05-10
1.26.2	14 / 11	2026-04-16
1.26.1	14 / 11	2026-04-16
1.26.0	14 / 11	2026-04-16
1.25.12	14 / 11	2026-03-31
1.25.11	14 / 11	2026-03-30
1.25.8	14 / 11	2026-03-02
1.25.6	14 / 11	2026-01-13
1.25.5	14 / 11	2026-01-13
1.25.4	14 / 11	2026-01-13
1.25.2	14 / 11	2025-12-22
1.25.1	14 / 11	2025-11-27
1.24.6	15 / 16	2025-11-16
1.24.2	15 / 15	2025-10-09
1.23.2	15 / 12	2025-10-06
1.23.0	15 / 12	2025-09-19
1.22.21	15 / 12	2025-09-10
1.22.20	15 / 12	2025-09-09
1.22.19	15 / 12	2025-09-08
1.22.18	15 / 12	2025-08-20
1.22.16	15 / 12	2025-07-29
1.22.15	15 / 12	2025-06-09
1.22.14	15 / 12	2025-06-09
1.22.13	15 / 12	2025-05-27
1.22.9	15 / 12	2025-05-14

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

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

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

v1.26.4

1 finding

LOW No provenance attestation provenance

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

v1.26.2

1 finding

LOW No provenance attestation provenance

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

v1.26.1

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.12

1 finding

LOW No provenance attestation provenance

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

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

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

v1.25.6

1 finding

LOW No provenance attestation provenance

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

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

v1.25.4

1 finding

LOW No provenance attestation provenance

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

v1.25.2

1 finding

LOW No provenance attestation provenance

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

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

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

v1.24.2

1 finding

LOW No provenance attestation provenance

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

v1.23.2

1 finding

LOW No provenance attestation provenance

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

v1.23.0

1 finding

LOW No provenance attestation provenance

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

v1.22.21

1 finding

LOW No provenance attestation provenance

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

v1.22.20

1 finding

LOW No provenance attestation provenance

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

v1.22.19

1 finding

LOW No provenance attestation provenance

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

v1.22.18

1 finding

LOW No provenance attestation provenance

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

v1.22.16

1 finding

LOW No provenance attestation provenance

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

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

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

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

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