@jaypie/fabric
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-peer-dep:@jaypie/aws | AI (dependencies): Optional peer dep from the same @jaypie monorepo; consumer-controlled and optional. | ai | |
| dependencies | unvetted-peer-dep:@jaypie/lambda | AI (dependencies): Optional peer dep from the same @jaypie monorepo; consumer-controlled and optional. | ai | |
| dependencies | unvetted-peer-dep:@jaypie/express | AI (dependencies): Optional peer dep from the same @jaypie monorepo; consumer-controlled and optional. | ai | |
| dependencies | unvetted-peer-dep:@jaypie/dynamodb | AI (dependencies): Optional peer dep from the same @jaypie monorepo; consumer-controlled and optional. | ai | |
| dependencies | unvetted-dep:@jaypie/errors | AI (dependencies): Sibling package in the same @jaypie monorepo/org; unvetted status reflects pipeline gap, not a security concern. Stable across versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 1 / 18 | |
| 0.3.1 | 1 / 17 | |
| 0.3.0 | 1 / 17 | |
| 0.2.4 | 1 / 17 | |
| 0.2.3 | 1 / 17 | |
| 0.2.2 | 1 / 17 | |
| 0.2.1 | 1 / 17 | |
| 0.2.0 | 1 / 17 | |
| 0.1.4 | 1 / 17 | |
| 0.1.3 | 1 / 17 | |
| 0.1.2 | 1 / 17 | |
| 0.1.1 | 1 / 17 | |
| 0.1.0 | 1 / 17 |
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.