← Home

@agoric/notifier

npm Repository Homepage

Notifier allows services to update clients about state changes using a stream of promises

9
Versions
Apache-2.0
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

warnererightsmhofmanmichaelfigkriskowalagoricbotmujahidkaygibson042jimlarsonsamsiegart

Keywords

notifier

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@agoric/marshal AI (dependencies): First-party Agoric monorepo sibling package. ai
maintainer-change maintainer-added AI (maintainer-change): Bot account addition consistent with org's CI publishing pattern. ai
dependencies unvetted-dep:@agoric/assert AI (dependencies): First-party Agoric monorepo package, same publisher/org. ai
publish-pattern new-deps-added AI (publish-pattern): Internal Agoric package rename/refactor, not third-party additions. ai
source-diff source-size-tripled AI (source-diff): Small absolute size increase consistent with added deps/functionality. ai

Versions (showing 9 of 9)

Version Deps Published
0.7.0 7 / 8
0.3.33 4 / 5
0.3.21 4 / 4
0.3.19 4 / 4
0.2.0 3 / 3
0.1.3 2 / 4
0.1.2 2 / 4
0.1.1 2 / 4
0.1.0 2 / 4

v0.3.33

1 finding
LOW No provenance attestation provenance

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

v0.3.21

1 finding
LOW No provenance attestation provenance

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

v0.3.19

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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