@icanbwell/bwell-sdk-ts
b.well TypeScript SDK
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change to icanbwell-admin reflects org-level account consolidation; stable for this package. | ai | |
| dependencies | unvetted-dep:@opentelemetry/instrumentation-fetch | AI (dependencies): Official OpenTelemetry package; stable, well-known CNCF project with no malicious indicators. | ai | |
| dependencies | unvetted-dep:@opentelemetry/instrumentation-xml-http-request | AI (dependencies): Official OpenTelemetry package; stable, well-known CNCF project with no malicious indicators. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-fetch | AI (phantom-deps): Referenced in config files only; legitimate OpenTelemetry instrumentation dep pattern for this SDK. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): Referenced in config files only; legitimate OpenTelemetry exporter dep pattern for this SDK. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.16.0 | 12 / 23 | |
| 1.15.0 | 12 / 23 | |
| 1.14.0 | 12 / 23 | |
| 1.13.0 | 12 / 23 | |
| 1.12.0 | 12 / 23 | |
| 1.11.0 | 12 / 23 | |
| 1.10.0 | 12 / 23 | |
| 1.9.0 | 12 / 23 | |
| 1.8.2 | 12 / 23 | |
| 1.8.0 | 12 / 23 | |
| 1.7.0 | 12 / 23 | |
| 1.6.0 | 12 / 23 | |
| 1.5.0 | 12 / 23 | |
| 1.4.0 | 12 / 23 | |
| 1.3.0 | 12 / 23 | |
| 1.2.0 | 12 / 23 | |
| 1.1.0 | 12 / 23 | |
| 1.0.0 | 12 / 23 |
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.