@furystack/repository
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@furystack/core | AI (dependencies): Same-monorepo sibling dependency; stable pattern across all @furystack/repository versions. | ai | |
| dependencies | unvetted-dep:@furystack/utils | AI (dependencies): Same-monorepo sibling dependency; stable pattern across all @furystack/repository versions. | ai | |
| dependencies | unvetted-dep:@furystack/inject | AI (dependencies): Same-monorepo sibling dependency; stable pattern across all @furystack/repository versions. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 11.0.2 | 3 / 2 | |
| 11.0.0 | 3 / 2 | |
| 10.1.11 | 3 / 2 | |
| 10.1.10 | 3 / 2 | |
| 10.1.9 | 3 / 2 | |
| 10.1.8 | 3 / 2 | |
| 10.1.7 | 3 / 2 | |
| 10.1.6 | 3 / 2 | |
| 10.1.5 | 3 / 2 | |
| 10.1.4 | 3 / 2 | |
| 10.1.1 | 3 / 2 | |
| 10.1.0 | 3 / 2 | |
| 10.0.37 | 3 / 2 | |
| 10.0.36 | 3 / 2 | |
| 10.0.35 | 3 / 2 | |
| 10.0.34 | 3 / 2 | |
| 10.0.33 | 3 / 2 | |
| 10.0.32 | 3 / 2 | |
| 10.0.31 | 3 / 2 | |
| 10.0.30 | 3 / 2 | |
| 10.0.29 | 3 / 2 |
v11.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.