← Home

observable

npm Repository Homepage

A function as representation of a trackable mutable value.

19
Versions
MIT
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

raynosdominictarr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change raynos→dominictarr occurred in Jan 2013 (12+ years ago); dominictarr is a well-known Node.js contributor and the repo URL confirms legitimate ownership transfer. ai
maintainer-change maintainer-added AI (maintainer-change): dominictarr is the confirmed new owner since 2013; this is a historical, legitimate maintainer transition, not a compromise. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is in example/static/demo.js — a demo file for interactive code evaluation. Not in production code paths; expected pattern for a live demo. ai
source-diff source-size-dropped AI (source-diff): Size drop explained by removal of several large runtime deps (dnode, eventemitter-light, node-uuid, pd) during a legitimate refactoring. ai

Versions (showing 19 of 19)

Version Deps Published
2.1.4 0 / 2
2.1.3 0 / 2
2.1.2 0 / 2
2.1.1 0 / 2
2.1.0 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2
1.4.2 0 / 2
1.4.1 0 / 2
1.4.0 0 / 2
1.3.1 0 / 2
1.3.0 0 / 2
1.2.0 0 / 2
1.1.1 0 / 2
1.1.0 1 / 1
1.0.0 1 / 0
0.1.3 4 / 3
0.1.2 4 / 3
0.1.1 4 / 3

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

2 findings
HIGH Publisher changed: raynos → dominictarr (on 2013-01-28) provenance

This version was published by a different npm account than previous versions on 2013-01-28. 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.