@furystack/security
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 package versions. | ai | |
| dependencies | unvetted-dep:@furystack/inject | AI (dependencies): Same-monorepo sibling dependency; stable pattern across all furystack package versions. | ai | |
| dependencies | unvetted-dep:@furystack/repository | AI (dependencies): Same-monorepo sibling dependency; stable pattern across all furystack package versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 3 / 4 | |
| 8.0.0 | 3 / 4 | |
| 7.0.9 | 3 / 4 | |
| 7.0.8 | 3 / 4 | |
| 7.0.7 | 3 / 4 | |
| 7.0.6 | 3 / 4 | |
| 7.0.5 | 3 / 4 | |
| 7.0.4 | 3 / 4 | |
| 7.0.3 | 3 / 4 | |
| 7.0.2 | 3 / 4 | |
| 6.0.38 | 2 / 4 | |
| 6.0.37 | 2 / 4 | |
| 6.0.36 | 2 / 4 | |
| 6.0.35 | 2 / 4 | |
| 6.0.34 | 2 / 4 | |
| 6.0.33 | 2 / 4 | |
| 6.0.32 | 2 / 4 | |
| 6.0.31 | 2 / 4 | |
| 6.0.30 | 2 / 4 | |
| 6.0.29 | 2 / 4 |
v8.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.