← Home

@orca-so/common-sdk

npm Repository Homepage

Common Typescript components across Orca

16
Versions
SEE LICENSE IN LICENSE
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

tmoc.orcayugure-orcawjthieme-orcaorcasysops

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Established 84-version SDK with 32.9k weekly downloads; short README / no keywords are cosmetic, not spam indicators. ai

Versions (showing 16 of 16)

Version Deps Published
0.7.1 2 / 3
0.7.0 2 / 3
0.6.11 2 / 3
0.6.10 2 / 3
0.6.9 1 / 4
0.6.8 1 / 4
0.6.7 1 / 4
0.6.6 1 / 4
0.6.5 1 / 4
0.6.4 1 / 3
0.6.3 1 / 3
0.6.2 1 / 3
0.6.1 1 / 3
0.6.0 1 / 3
0.5.7 1 / 0
0.5.6 1 / 0

v0.7.1

2 findings
HIGH Publisher changed: wjthieme-orca → orcasysops (on 2026-07-01) provenance

This version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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

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

v0.6.5

1 finding
LOW No provenance attestation provenance

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

v0.6.4

1 finding
LOW No provenance attestation provenance

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

v0.6.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wjthieme-orca → meep.orca (on 2024-08-28, known maintainer) provenance

This version was published by a different npm account (meep.orca) than the most recent previously approved version (wjthieme-orca) on 2024-08-28, but meep.orca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: meep.orca → wjthieme-orca (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (wjthieme-orca) than the most recent previously approved version (meep.orca) on 2024-08-06, but wjthieme-orca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yugure-orca → meep.orca (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (meep.orca) than the most recent previously approved version (yugure-orca) on 2024-08-06, but meep.orca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wjthieme-orca → yugure-orca (on 2024-06-17, known maintainer) provenance

This version was published by a different npm account (yugure-orca) than the most recent previously approved version (wjthieme-orca) on 2024-06-17, but yugure-orca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.7

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