@de-otio/trellis
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:@aws-sdk/client-ssm | AI (phantom-deps): AWS SDK packages are often loaded by convention/framework; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/s3-request-presigner | AI (phantom-deps): AWS SDK packages are often loaded by convention/framework; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Config-referenced dependency; stable for this monorepo package. | ai | |
| phantom-deps | phantom-dep:isomorphic-dompurify | AI (phantom-deps): Config-referenced dependency; stable for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@prisma/extension-accelerate | AI (phantom-deps): Config-referenced dependency; stable for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo workspace package; missing metadata is expected for internal components. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.10.6 | 30 / 20 | |
| 0.10.5 | 30 / 20 | |
| 0.10.4 | 30 / 20 | |
| 0.10.3 | 30 / 20 | |
| 0.10.2 | 30 / 20 | |
| 0.10.1 | 30 / 20 | |
| 0.10.0 | 30 / 20 | |
| 0.9.0 | 30 / 20 | |
| 0.7.1 | 25 / 21 | |
| 0.7.0 | 23 / 23 | |
| 0.6.1 | 23 / 22 | |
| 0.6.0 | 22 / 22 | |
| 0.5.0 | 22 / 22 | |
| 0.4.0 | 22 / 22 |
v0.10.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.