← Home

@uniformdev/canvas-next-rsc-client

npm
73
Versions
SEE LICENSE IN LICENSE.txt
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

drolexanalenpelinkamsaradamluniformoriginalexem1r1kjakub-uniformserhiiouniformdev

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped SDK sub-package in a large monorepo; sparse metadata is typical for this package family. ai
npm-metadata no-description AI (npm-metadata): Consistent pattern across @uniformdev scoped packages; not a spam/malware indicator here. ai

Versions (showing 73 of 73)

Version Deps Published
20.73.0 4 / 7
20.72.3 4 / 7
20.72.2 4 / 7
20.72.1 4 / 7
20.71.1 4 / 7
20.71.0 4 / 7
20.70.0 4 / 7
20.69.0 4 / 7
20.68.0 4 / 7
20.67.0 4 / 7
20.66.6 4 / 7
20.66.4 4 / 7
20.66.2 4 / 7
20.66.1 4 / 7
20.66.0 4 / 7
20.65.0 4 / 7
20.64.0 4 / 7
20.63.0 4 / 7
20.61.1 4 / 7
20.60.2 4 / 7
20.60.1 4 / 7
20.60.0 4 / 7
20.59.1 4 / 7
20.58.0 4 / 7
20.57.1 4 / 7
20.56.0 4 / 7
20.55.2 4 / 7
20.55.1 4 / 7
20.55.0 4 / 7
20.54.0 4 / 7
20.53.1 4 / 7
20.53.0 4 / 7
20.51.0 4 / 7
20.50.2 4 / 7
20.50.1 4 / 7
20.50.0 4 / 7
20.49.4 4 / 7
20.49.3 4 / 7
20.49.2 4 / 7
20.49.1 4 / 7
20.49.0 4 / 7
20.48.0 4 / 7
20.47.1 4 / 7
20.47.0 4 / 7
20.46.0 4 / 7
20.45.0 4 / 7
20.43.1 4 / 7
20.43.0 3 / 6
20.42.1 3 / 6
20.42.0 3 / 6
20.41.0 3 / 6
20.24.0 3 / 6
20.23.0 3 / 6
20.20.3 3 / 6
20.20.0 3 / 6
20.18.0 3 / 6
20.16.0 3 / 6
20.15.0 3 / 6
20.14.2 3 / 6
20.14.1 3 / 6
20.14.0 3 / 6
20.13.2 3 / 6
20.13.0 3 / 6
20.11.0 3 / 7
20.10.0 3 / 7
20.9.0 3 / 7
20.8.1 3 / 7
20.6.1 3 / 7
20.5.0 3 / 7
20.3.1 3 / 7
20.2.0 3 / 7
20.1.0 3 / 7
20.0.0 3 / 7

v20.73.0

1 finding
LOW No provenance attestation provenance

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

v20.72.3

1 finding
LOW No provenance attestation provenance

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

v20.72.2

1 finding
LOW No provenance attestation provenance

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

v20.72.1

1 finding
LOW No provenance attestation provenance

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

v20.71.1

1 finding
LOW No provenance attestation provenance

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

v20.71.0

1 finding
LOW No provenance attestation provenance

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

v20.70.0

1 finding
LOW No provenance attestation provenance

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

v20.69.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

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