@strapi/helper-plugin
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:react-select | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:react-helmet | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:formik | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:react-intl | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:react-query | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Common Strapi runtime dep, false positive from bundled build. | ai | |
| source-diff | obfuscated-file-transition:dist/content-manager/utils/contentManagementUtilRemoveFieldsFromData.d.ts | AI (source-diff): Long-line .d.ts is complex TS generic type, not obfuscation. | ai | |
| source-diff | obfuscated-file-transition:dist/content-manager/utils/formatContentTypeData.d.ts | AI (source-diff): Long-line .d.ts is complex TS generic type, not obfuscation. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Same as above. | ai | |
| phantom-deps | phantom-dep:immutable | AI (phantom-deps): Same as above. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established 74k/wk scoped Strapi package; README/keyword heuristics are FPs here. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Standard React peer dep, used in unscanned source. | ai | |
| phantom-deps | phantom-dep:match-sorter | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:react-router | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:mini-css-extract-plugin | AI (phantom-deps): Webpack build tool dep, not expected in source imports. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-free | AI (phantom-deps): CSS/asset-only fontawesome package, not imported as JS. | ai | |
| phantom-deps | phantom-dep:@fortawesome/react-fontawesome | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:babel-plugin-styled-components | AI (phantom-deps): Babel plugin, referenced in babel config not source imports. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-brands-svg-icons | AI (phantom-deps): Used in unscanned source, only build output scanned. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Common prop-types false positive in bundled React libs. | ai | |
| phantom-deps | phantom-dep:immer | AI (phantom-deps): Bundled build output; immer likely used internally, no scannable import. | ai |
Versions (showing 56 of 156)
| Version | Deps | Published |
|---|---|---|
| 4.8.0 | 10 / 24 | |
| 4.7.1 | 9 / 22 | |
| 4.7.0 | 9 / 22 | |
| 4.6.2 | 9 / 22 | |
| 4.6.1 | 17 / 17 | |
| 4.6.0 | 17 / 17 | |
| 4.5.6 | 17 / 16 | |
| 4.5.5 | 17 / 16 | |
| 4.5.4 | 22 / 16 | |
| 4.5.3 | 22 / 16 | |
| 4.5.2 | 22 / 16 | |
| 4.5.1 | 22 / 16 | |
| 4.5.0 | 22 / 16 | |
| 4.4.7 | 22 / 16 | |
| 4.4.6 | 22 / 16 | |
| 4.4.5 | 23 / 24 | |
| 4.4.4 | 23 / 24 | |
| 4.4.3 | 23 / 24 | |
| 4.4.2 | 23 / 24 | |
| 4.4.1 | 22 / 24 | |
| 4.4.0 | 22 / 24 | |
| 4.3.9 | 22 / 24 | |
| 4.3.8 | 22 / 24 | |
| 4.3.7 | 22 / 24 | |
| 4.3.6 | 22 / 24 | |
| 4.3.5 | 22 / 24 | |
| 4.3.4 | 19 / 20 | |
| 4.3.3 | 19 / 20 | |
| 4.3.2 | 19 / 20 | |
| 4.3.1 | 19 / 20 | |
| 4.3.0 | 19 / 20 | |
| 4.2.3 | 19 / 20 | |
| 4.2.2 | 19 / 20 | |
| 4.2.0 | 21 / 20 | |
| 4.1.12 | 21 / 20 | |
| 4.1.11 | 21 / 20 | |
| 4.1.10 | 21 / 20 | |
| 4.1.9 | 21 / 20 | |
| 4.1.8 | 21 / 20 | |
| 4.1.7 | 21 / 20 | |
| 4.1.6 | 21 / 20 | |
| 4.1.5 | 21 / 20 | |
| 4.1.4 | 21 / 20 | |
| 4.1.3 | 21 / 22 | |
| 4.1.2 | 21 / 22 | |
| 4.1.1 | 21 / 22 | |
| 4.1.0 | 21 / 22 | |
| 4.0.8 | 21 / 22 | |
| 4.0.7 | 21 / 22 | |
| 4.0.6 | 21 / 22 | |
| 4.0.5 | 21 / 22 | |
| 4.0.4 | 21 / 22 | |
| 4.0.3 | 21 / 22 | |
| 4.0.2 | 23 / 22 | |
| 4.0.1 | 23 / 22 | |
| 4.0.0 | 22 / 22 |
v4.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (convly) than the most recent previously approved version (alexandrebodin) on 2023-03-15, but convly is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.7.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexandrebodin) than the most recent previously approved version (convly) on 2023-03-02, but alexandrebodin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.