← Home

three-csg-ts

npm Repository Homepage
18
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

samalexander

Keywords

threethreejsthree-jscsgcomputational-solid-geometry

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:jiro.digital AI (email-domain): No behavioral change; long-standing publisher with clean history, no exploit evidence. ai
publish-pattern dormant-publish AI (publish-pattern): Diff shows no material changes; dormancy alone isn't a takeover indicator here. ai

Versions (showing 18 of 18)

Version Deps Published
3.2.0 0 / 22
3.1.14 0 / 22
3.1.13 0 / 22
3.1.12 0 / 22
3.1.11 0 / 22
3.1.10 0 / 22
3.1.9 0 / 22
3.1.8 0 / 22
3.1.7 0 / 22
3.1.6 0 / 22
3.1.5 0 / 22
3.1.4 0 / 22
3.1.3 0 / 22
3.1.2 0 / 22
3.1.1 0 / 22
3.1.0 0 / 22
3.0.1 0 / 22
3.0.0 0 / 22

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.14

2 findings
HIGH Unclaimed maintainer email domain: jiro.digital email-domain

Maintainer email '[email protected]' uses domain 'jiro.digital' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.13

2 findings
HIGH Unclaimed maintainer email domain: jiro.digital email-domain

Maintainer email '[email protected]' uses domain 'jiro.digital' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.12

2 findings
HIGH Unclaimed maintainer email domain: jiro.digital email-domain

Maintainer email '[email protected]' uses domain 'jiro.digital' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.11

2 findings
HIGH Unclaimed maintainer email domain: jiro.digital email-domain

Maintainer email '[email protected]' uses domain 'jiro.digital' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.10

2 findings
HIGH Unclaimed maintainer email domain: jiro.digital email-domain

Maintainer email '[email protected]' uses domain 'jiro.digital' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.9

1 finding
LOW No provenance attestation provenance

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

v3.1.8

1 finding
LOW No provenance attestation provenance

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

v3.1.7

1 finding
LOW No provenance attestation provenance

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

v3.1.6

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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