@verii/base-contract-io
Package contains functions needed across all contract io packages
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:@verii/common-functions | AI (phantom-deps): Same-org dependency (@verii scope); likely re-exported or used indirectly within the monorepo. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@verii/http-client | AI (dependencies): Same-org scoped package from the @verii monorepo, released in lockstep at the same version. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@verii/common-functions | AI (dependencies): Same-org scoped package from the @verii monorepo, released in lockstep at the same version. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@verii/blockchain-functions | AI (dependencies): Same-org scoped package from the @verii monorepo, released in lockstep at the same version. Not an independent risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; sparse README and missing keywords are cosmetic, not security signals. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 7 / 4 | |
| 1.1.2 | 7 / 4 | |
| 1.1.1 | 7 / 4 | |
| 1.1.0 | 7 / 4 | |
| 1.0.9 | 7 / 4 | |
| 1.0.8 | 7 / 4 | |
| 1.0.7 | 7 / 4 | |
| 1.0.6 | 7 / 4 | |
| 1.0.5 | 7 / 4 | |
| 1.0.4 | 7 / 4 | |
| 1.0.3 | 7 / 4 | |
| 1.0.2 | 7 / 4 | |
| 1.0.1 | 7 / 4 | |
| 1.0.0 | 7 / 4 |
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.