@freesail/core
Core TypeScript logic for Freesail - protocol definitions, parser, transport
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @freesail/core is clearly not impersonating 'cors'; name reflects its own project identity. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): vite is listed as a runtime dep but used as a build tool; likely a packaging error, not malicious. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.9.2 | 1 / 1 | |
| 0.9.1 | 1 / 1 | |
| 0.9.0 | 1 / 1 | |
| 0.8.9 | 1 / 1 | |
| 0.8.8 | 1 / 1 | |
| 0.8.7 | 1 / 1 | |
| 0.8.6 | 1 / 1 | |
| 0.8.5 | 1 / 1 | |
| 0.8.4 | 1 / 1 | |
| 0.8.3 | 1 / 1 | |
| 0.8.2 | 1 / 1 | |
| 0.8.1 | 1 / 1 | |
| 0.7.2 | 1 / 1 | |
| 0.7.1 | 1 / 1 | |
| 0.4.6 | 1 / 1 | |
| 0.4.5 | 1 / 1 | |
| 0.4.3 | 1 / 1 |
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
2 findingsPackage name '@freesail/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.
v0.8.8
2 findingsPackage name '@freesail/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.
v0.8.7
2 findingsPackage name '@freesail/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.
v0.8.6
2 findingsPackage name '@freesail/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.
v0.8.5
2 findingsPackage name '@freesail/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.
v0.8.4
2 findingsPackage name '@freesail/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.
v0.8.3
2 findingsPackage name '@freesail/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.
v0.8.2
2 findingsPackage name '@freesail/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.
v0.8.1
2 findingsPackage name '@freesail/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.
v0.7.2
2 findingsPackage name '@freesail/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.
v0.7.1
2 findingsPackage name '@freesail/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.
v0.4.6
2 findingsPackage name '@freesail/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.
v0.4.5
2 findingsPackage name '@freesail/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.
v0.4.3
2 findingsPackage name '@freesail/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.