@dxos/plugin-files
DXOS Surface plugin for managing files.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dxos/react-ui-data | AI (dependencies): Same-org monorepo sibling published in lockstep, not a third-party dependency. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @dxos/* packages from the same monorepo release. | ai | |
| bogus-package | bogus-package | AI (bogus-package): DXOS monorepo component; sparse README is typical for internal plugin packages, not spam. | ai | |
| phantom-deps | phantom-dep:@dxos/echo | AI (phantom-deps): Same-org monorepo dep; may be transitively used rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@dxos/echo-schema | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for bundled ESM packages. | ai | |
| phantom-deps | phantom-dep:@dxos/plugin-theme | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for bundled ESM packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 20 / 12 | |
| 0.8.2 | 20 / 12 | |
| 0.8.1 | 19 / 9 | |
| 0.8.0 | 19 / 9 | |
| 0.7.4 | 15 / 9 | |
| 0.7.3 | 15 / 9 | |
| 0.7.2 | 15 / 9 | |
| 0.7.1 | 15 / 9 | |
| 0.7.0 | 15 / 9 | |
| 0.6.13 | 13 / 9 | |
| 0.6.12 | 13 / 9 | |
| 0.6.11 | 13 / 9 | |
| 0.6.10 | 13 / 9 | |
| 0.6.9 | 13 / 9 | |
| 0.6.8 | 13 / 9 |
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.