@orama/plugin-data-persistence
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Orama org packages consistently publish without Sigstore provenance; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.1.18 | 4 / 14 | |
| 3.1.17 | 4 / 14 | |
| 3.1.16 | 4 / 14 | |
| 3.1.15 | 4 / 14 | |
| 3.1.14 | 4 / 14 | |
| 3.1.13 | 4 / 14 | |
| 3.1.12 | 3 / 13 | |
| 3.1.11 | 3 / 13 | |
| 3.1.10 | 3 / 13 | |
| 3.1.9 | 3 / 13 | |
| 3.1.7 | 3 / 13 | |
| 3.1.6 | 3 / 13 | |
| 3.1.5 | 3 / 13 | |
| 3.1.4 | 3 / 13 | |
| 3.1.3 | 3 / 13 | |
| 3.1.2 | 3 / 13 | |
| 3.1.1 | 3 / 13 | |
| 3.1.0 | 3 / 13 | |
| 3.0.8 | 3 / 13 | |
| 3.0.7 | 3 / 13 | |
| 3.0.6 | 3 / 13 | |
| 3.0.5 | 3 / 13 | |
| 3.0.4 | 3 / 13 | |
| 3.0.3 | 3 / 13 | |
| 3.0.2 | 3 / 13 | |
| 3.0.1 | 3 / 13 | |
| 3.0.0 | 3 / 13 |
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.