@yuants/data-model
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Used in config/type defs, not a real risk. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Used in config, not a real risk. | ai | |
| phantom-deps | phantom-dep:date-fns-tz | AI (phantom-deps): Used in config, not a real risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package, not unvetted third-party. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.19.3 | 5 / 10 | |
| 0.19.2 | 5 / 10 | |
| 0.19.1 | 5 / 10 | |
| 0.19.0 | 5 / 10 | |
| 0.18.5 | 5 / 10 | |
| 0.18.4 | 5 / 10 | |
| 0.18.3 | 5 / 10 | |
| 0.18.2 | 5 / 10 | |
| 0.18.1 | 5 / 10 | |
| 0.18.0 | 4 / 10 | |
| 0.17.8 | 4 / 10 | |
| 0.17.7 | 4 / 10 | |
| 0.17.6 | 4 / 10 | |
| 0.17.5 | 4 / 10 | |
| 0.17.4 | 4 / 10 | |
| 0.17.3 | 4 / 10 | |
| 0.17.2 | 4 / 10 | |
| 0.17.1 | 4 / 10 | |
| 0.17.0 | 4 / 10 | |
| 0.16.0 | 4 / 10 | |
| 0.15.0 | 4 / 10 | |
| 0.14.0 | 4 / 10 | |
| 0.13.0 | 4 / 10 | |
| 0.12.0 | 4 / 10 | |
| 0.7.0 | 4 / 10 |
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.