← Home

@smithers-orchestrator/observability

npm
17
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

fucory

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@smithers-orchestrator/memory AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. Consistent pattern with other accepted phantom deps in this package. ai
phantom-deps phantom-dep:@smithers-orchestrator/openapi AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. ai
phantom-deps phantom-dep:@smithers-orchestrator/scorers AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. ai
phantom-deps phantom-dep:@smithers-orchestrator/time-travel AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported. ai
phantom-deps phantom-dep:@smithers-orchestrator/agents AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly, not a true phantom. ai
phantom-deps phantom-dep:@smithers-orchestrator/driver AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly, not a true phantom. ai

Versions (showing 17 of 17)

Version Deps Published
0.23.0 5 / 2
0.22.0 5 / 2
0.21.0 5 / 2
0.20.4 5 / 2
0.20.0 10 / 2
0.19.0 10 / 2
0.18.0 10 / 2
0.17.0 10 / 2
0.16.9 6 / 2
0.16.8 6 / 2
0.16.7 6 / 2
0.16.6 6 / 2
0.16.5 6 / 2
0.16.4 6 / 2
0.16.3 6 / 2
0.16.1 6 / 2
0.16.0 6 / 2

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.4

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

v0.19.0

1 finding
LOW No provenance attestation provenance

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

v0.18.0

1 finding
LOW No provenance attestation provenance

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

v0.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.9

1 finding
LOW No provenance attestation provenance

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

v0.16.8

1 finding
LOW No provenance attestation provenance

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

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

v0.16.5

1 finding
LOW No provenance attestation provenance

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

v0.16.4

1 finding
LOW No provenance attestation provenance

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

v0.16.3

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

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