@mars-stack/core
Core infrastructure for MARS apps -- auth, database, rate limiting, email, logging, and more.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package published via GitHub Actions; lack of Sigstore provenance is informational, not a security concern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @mars-stack/core is a scoped SaaS framework package; similarity to 'cors' is incidental word overlap, not impersonation. Stable false positive for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs a local script (node scripts/postinstall.mjs) included in published files. Consistent with framework setup tasks (e.g. Prisma). No obfuscation or network-exec signals present. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 11.0.2 | 4 / 17 | |
| 9.0.9 | 4 / 17 | |
| 9.0.8 | 4 / 17 | |
| 9.0.7 | 4 / 17 | |
| 9.0.4 | 4 / 17 | |
| 9.0.1 | 4 / 17 | |
| 9.0.0 | 4 / 17 | |
| 8.0.37 | 4 / 17 | |
| 8.0.36 | 4 / 17 | |
| 8.0.33 | 4 / 17 | |
| 8.0.31 | 4 / 17 | |
| 8.0.27 | 4 / 17 | |
| 8.0.24 | 4 / 17 | |
| 8.0.21 | 4 / 17 | |
| 8.0.20 | 4 / 17 | |
| 8.0.17 | 4 / 17 | |
| 8.0.16 | 4 / 17 | |
| 8.0.14 | 4 / 17 | |
| 8.0.12 | 4 / 17 | |
| 8.0.11 | 4 / 17 | |
| 8.0.8 | 4 / 17 | |
| 8.0.7 | 4 / 17 | |
| 8.0.5 | 4 / 17 | |
| 8.0.2 | 4 / 17 | |
| 8.0.0 | 4 / 17 | |
| 7.0.6 | 4 / 17 | |
| 7.0.5 | 4 / 17 | |
| 7.0.4 | 4 / 17 | |
| 7.0.3 | 4 / 17 | |
| 7.0.2 | 4 / 17 | |
| 7.0.0 | 4 / 17 | |
| 6.0.4 | 4 / 17 | |
| 6.0.3 | 4 / 17 | |
| 6.0.2 | 4 / 17 | |
| 6.0.0 | 4 / 17 | |
| 5.0.3 | 4 / 17 | |
| 5.0.1 | 4 / 17 | |
| 4.0.0 | 4 / 17 | |
| 3.0.0 | 4 / 17 | |
| 2.0.1 | 4 / 17 | |
| 2.0.0 | 4 / 17 | |
| 1.0.2 | 4 / 17 | |
| 0.4.1 | 4 / 17 | |
| 0.4.0 | 4 / 17 |
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.7
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.37
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.36
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.33
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.31
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.27
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.24
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.21
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.20
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.17
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.16
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.14
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.12
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.11
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.8
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.7
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
3 findingsScript: node scripts/postinstall.mjs
Package name '@mars-stack/core' is 1 edit(s) away from popular package 'cors'.
Package 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.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.