dtable-store
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Organizational package with 1157 versions and 2319 days history; sparse metadata is a stable pattern, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal Seafile package; not a malware signal here. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Bundled dist-only package; deps used at build time may not appear as direct imports. | ai | |
| phantom-deps | phantom-dep:slugid | AI (phantom-deps): Same bundled dist pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:deep-copy | AI (phantom-deps): Same bundled dist pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dtable-utils | AI (phantom-deps): Same bundled dist pattern; stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 6.2.7 | 7 / 36 | |
| 6.2.6 | 7 / 36 | |
| 6.2.5 | 7 / 36 | |
| 6.2.4 | 7 / 36 | |
| 6.2.3 | 7 / 36 | |
| 6.2.2 | 7 / 36 | |
| 6.2.1 | 7 / 37 | |
| 6.2.0 | 7 / 37 | |
| 6.1.7 | 7 / 38 | |
| 6.1.6 | 7 / 38 | |
| 6.1.5 | 7 / 38 | |
| 6.1.4 | 7 / 38 | |
| 6.1.3 | 7 / 38 | |
| 6.1.2 | 7 / 38 | |
| 6.1.1 | 7 / 38 | |
| 6.1.0 | 7 / 38 | |
| 6.0.11 | 7 / 38 | |
| 6.0.10 | 7 / 38 | |
| 6.0.9 | 7 / 38 | |
| 6.0.8 | 7 / 38 | |
| 6.0.7 | 7 / 38 | |
| 6.0.6 | 7 / 38 | |
| 6.0.5 | 7 / 38 | |
| 6.0.4 | 7 / 38 | |
| 6.0.3 | 7 / 38 | |
| 6.0.2 | 7 / 38 | |
| 6.0.1 | 7 / 38 | |
| 6.0.0 | 7 / 38 |
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.