@bosonprotocol/core-sdk
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared runtime dep used by graphql-request; phantom-dep false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.48.0 | 14 / 7 | |
| 1.47.0 | 13 / 7 | |
| 1.46.1 | 13 / 7 | |
| 1.22.0 | 12 / 6 | |
| 1.21.0 | 12 / 6 | |
| 1.20.1 | 12 / 6 | |
| 1.20.0 | 12 / 6 | |
| 1.19.1 | 12 / 6 | |
| 1.19.0 | 12 / 6 | |
| 1.18.0 | 12 / 6 | |
| 1.17.0 | 12 / 6 | |
| 1.16.0 | 12 / 6 |
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bosonprotocoladmin) than the most recent previously approved version (dohaki_boson) on 2022-10-12, but bosonprotocoladmin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.