@wovin/connect-web3storage
Utilities for interacting with web3.storage services, including IPNS name watching.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:besonders-logger | AI (dependencies): Pinned to exact version 1.0.1, phantom-dep finding suggests it's only referenced in config; low risk for this package. | ai | |
| dependencies | unvetted-dep:w3name | AI (dependencies): w3name is a well-known web3.storage/Protocol Labs library; stable dependency for this package. | ai | |
| license | copyleft-license:AGPL-3.0-or-later | AI (license): Package is intentionally AGPL-3.0; stable licensing choice for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@wovin/core | AI (phantom-deps): Same-org monorepo peer dependency; not directly imported but legitimately declared as a runtime dep. | ai | |
| phantom-deps | phantom-dep:@ipld/car | AI (phantom-deps): Build tool / bundler config reference; not a direct import but legitimately declared as a dependency. | ai | |
| phantom-deps | phantom-dep:besonders-logger | AI (phantom-deps): Logging dependency referenced in config; stable false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.3.6 | 1 / 5 | |
| 0.3.5 | 1 / 5 | |
| 0.3.4 | 1 / 5 | |
| 0.3.3 | 1 / 5 | |
| 0.3.2 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.2 | 6 / 5 | |
| 0.2.0 | 6 / 5 | |
| 0.1.36 | 6 / 5 | |
| 0.1.33 | 6 / 5 | |
| 0.1.32 | 6 / 5 | |
| 0.1.27 | 6 / 5 | |
| 0.1.25 | 6 / 5 | |
| 0.1.24 | 6 / 5 | |
| 0.1.23 | 6 / 5 | |
| 0.1.22 | 6 / 5 | |
| 0.1.21 | 6 / 5 | |
| 0.1.20 | 6 / 5 | |
| 0.1.19 | 6 / 5 | |
| 0.1.17 | 6 / 5 | |
| 0.1.15 | 6 / 5 | |
| 0.1.13 | 6 / 5 | |
| 0.1.11 | 6 / 5 | |
| 0.1.9 | 6 / 5 | |
| 0.1.8 | 6 / 5 | |
| 0.1.7 | 6 / 5 | |
| 0.1.6 | 6 / 5 | |
| 0.1.5 | 5 / 5 | |
| 0.1.4 | 5 / 5 | |
| 0.1.3 | 5 / 5 | |
| 0.1.2 | 5 / 5 | |
| 0.1.1 | 5 / 5 | |
| 0.0.26 | 5 / 5 | |
| 0.0.25 | 5 / 5 | |
| 0.0.6 | 4 / 5 | |
| 0.0.5 | 4 / 5 | |
| 0.0.4 | 4 / 5 | |
| 0.0.2 | 4 / 5 | |
| 0.0.1 | 4 / 5 |
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.