@osdk/faux
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:decimal.js | AI (phantom-deps): Monorepo bundling pattern; declared dep used transitively or in config, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:fetch-retry | AI (phantom-deps): Monorepo bundling pattern; declared dep used transitively or in config, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@osdk/foundry.geo | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is a false positive for monorepo re-exports. | ai | |
| phantom-deps | phantom-dep:json-stable-stringify | AI (phantom-deps): Monorepo bundling pattern; declared dep used transitively or in config, not a phantom risk. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 17 / 7 | |
| 0.23.0 | 17 / 7 | |
| 0.22.0 | 17 / 7 | |
| 0.21.0 | 17 / 7 | |
| 0.20.0 | 17 / 7 | |
| 0.19.0 | 17 / 7 | |
| 0.18.0 | 17 / 7 | |
| 0.17.0 | 17 / 7 | |
| 0.16.0 | 17 / 7 | |
| 0.14.0 | 17 / 7 | |
| 0.13.0 | 17 / 7 | |
| 0.12.0 | 17 / 7 | |
| 0.11.0 | 17 / 7 | |
| 0.10.0 | 17 / 7 | |
| 0.9.0 | 17 / 7 | |
| 0.8.0 | 17 / 7 | |
| 0.7.0 | 17 / 7 | |
| 0.6.0 | 17 / 7 | |
| 0.5.0 | 18 / 7 | |
| 0.4.0 | 17 / 7 | |
| 0.3.0 | 15 / 7 | |
| 0.2.2 | 15 / 7 | |
| 0.2.1 | 15 / 7 | |
| 0.2.0 | 15 / 7 | |
| 0.1.4 | 15 / 7 | |
| 0.1.3 | 15 / 7 | |
| 0.1.2 | 15 / 7 | |
| 0.1.1 | 15 / 7 | |
| 0.1.0 | 15 / 7 |
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
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.8.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.