@jaypie/fabricator
Seeded, deterministic test data generation built on @faker-js/faker
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Early-stage scoped org package (@jaypie); missing metadata is a hygiene issue, not a malicious indicator. Package structure is consistent with a legitimate library. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is declared as a dependency and consistent with a fabricator/test-data package; phantom detection likely due to indirect or config-level usage. Not a security concern. | ai | |
| provenance | slsa-provenance | AI (provenance): Package is consistently published via CI/CD with SLSA provenance; this is a stable positive signal for the jaypie ecosystem. | ai | |
| phantom-deps | phantom-dep:@jaypie/errors | AI (phantom-deps): Same-org sibling package; phantom dep finding is expected for intra-monorepo dependencies in the jaypie ecosystem. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 4 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.2.0 | 4 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 |
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
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.