@nocobase/plugin-field-attachment-url
Supports attachments in URL format.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/client/8ab1917056f663a6.js | AI (source-diff): Standard webpack-minified client bundle for a NocoBase plugin; copyright header and UI component content confirm legitimate build output. | ai | |
| source-diff | obfuscated-file:dist/client/542.543ddc65c8dc2137.js | AI (source-diff): Standard webpack-minified client bundle for a NocoBase plugin; copyright header and chunk naming confirm legitimate build output. Expected pattern for all @nocobase/* plugin packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the @nocobase/* scoped plugin ecosystem with 394 versions and 1.6k weekly downloads. Missing repo URL and link-dump README are consistent across all NocoBase plugins, not spam indicators. | ai | |
| source-diff | obfuscated-file:dist/client/db5199e8e877d42c.js | AI (source-diff): Standard webpack-minified client bundle for a NocoBase frontend plugin. The file header and content are consistent with legitimate build output from the NocoBase monorepo. | ai |
Versions (showing 26 of 126)
| Version | Deps | Published |
|---|---|---|
| 1.9.23 | 0 / 0 | |
| 1.9.22 | 0 / 0 | |
| 1.9.21 | 0 / 0 | |
| 1.9.20 | 0 / 0 | |
| 1.9.19 | 0 / 0 | |
| 1.9.18 | 0 / 0 | |
| 1.9.17 | 0 / 0 | |
| 1.9.16 | 0 / 0 | |
| 1.9.15 | 0 / 0 | |
| 1.9.14 | 0 / 0 | |
| 1.9.13 | 0 / 0 | |
| 1.9.12 | 0 / 0 | |
| 1.9.11 | 0 / 0 | |
| 1.9.10 | 0 / 0 | |
| 1.9.9 | 0 / 0 | |
| 1.9.8 | 0 / 0 | |
| 1.9.7 | 0 / 0 | |
| 1.9.6 | 0 / 0 | |
| 1.9.5 | 0 / 0 | |
| 1.9.4 | 0 / 0 | |
| 1.9.3 | 0 / 0 | |
| 1.9.2 | 0 / 0 | |
| 1.9.1 | 0 / 0 | |
| 1.9.0 | 0 / 0 | |
| 1.8.33 | 0 / 0 | |
| 1.8.32 | 0 / 0 |
v1.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.