@strapi/generate-new
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
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.26.2 | 11 / 2 | |
| 4.26.1 | 11 / 2 | |
| 4.26.0 | 11 / 2 | |
| 4.25.24 | 11 / 2 | |
| 4.25.23 | 11 / 2 | |
| 4.25.22 | 11 / 2 | |
| 4.25.21 | 11 / 2 | |
| 4.25.20 | 11 / 2 | |
| 4.25.19 | 11 / 2 | |
| 4.25.18 | 11 / 2 | |
| 4.25.17 | 11 / 2 | |
| 4.25.16 | 11 / 2 | |
| 4.25.15 | 11 / 2 | |
| 4.25.14 | 11 / 2 | |
| 4.25.13 | 11 / 2 | |
| 4.25.12 | 11 / 2 | |
| 4.25.11 | 11 / 2 | |
| 4.25.10 | 11 / 2 | |
| 4.25.9 | 11 / 2 | |
| 4.25.8 | 11 / 2 | |
| 4.25.7 | 11 / 2 | |
| 4.25.6 | 11 / 2 | |
| 4.25.5 | 11 / 2 | |
| 4.25.4 | 11 / 2 | |
| 4.25.3 | 11 / 2 | |
| 4.25.2 | 11 / 2 | |
| 4.25.1 | 11 / 2 | |
| 4.25.0 | 11 / 2 |
v4.25.22
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 (remidej) than the most recent previously approved version (marc-roig-strapi) on 2025-03-19, but remidej 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.25.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.20
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 (marc-roig-strapi) than the most recent previously approved version (baronvoninternet) on 2025-01-22, but marc-roig-strapi 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.25.19
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 (baronvoninternet) than the most recent previously approved version (convly) on 2025-01-09, but baronvoninternet 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.25.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.17
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 (baronvoninternet) on 2024-11-21, 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.25.16
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 (baronvoninternet) than the most recent previously approved version (remidej) on 2024-11-13, but baronvoninternet 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.25.15
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 (remidej) than the most recent previously approved version (marc-roig-strapi) on 2024-10-30, but remidej 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.25.14
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 (marc-roig-strapi) than the most recent previously approved version (remidej) on 2024-10-23, but marc-roig-strapi 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.25.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.11
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 (remidej) than the most recent previously approved version (marc-roig-strapi) on 2024-09-11, but remidej 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.25.10
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 (marc-roig-strapi) than the most recent previously approved version (convly) on 2024-09-04, but marc-roig-strapi 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.25.9
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 (marc-roig-strapi) on 2024-08-28, 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.25.8
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 (marc-roig-strapi) than the most recent previously approved version (remidej) on 2024-08-14, but marc-roig-strapi 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.25.7
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 (remidej) on 2024-08-07, 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.25.6
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 (remidej) than the most recent previously approved version (marc-roig-strapi) on 2024-07-31, but remidej 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.25.5
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 (marc-roig-strapi) than the most recent previously approved version (remidej) on 2024-07-24, but marc-roig-strapi 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.25.4
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 (marc-roig-strapi) than the most recent previously approved version (remidej) on 2024-07-17, but marc-roig-strapi 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.25.3
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 (remidej) than the most recent previously approved version (marc-roig-strapi) on 2024-07-10, but remidej 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.25.2
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 (marc-roig-strapi) than the most recent previously approved version (convly) on 2024-07-03, but marc-roig-strapi 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.25.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 (convly) than the most recent previously approved version (marc-roig-strapi) on 2024-06-19, 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.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.