@bobfrankston/gcal
Google Calendar CLI tool with ICS import support
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 | missing-githead | AI (provenance): Publish environment change is noted but no malicious indicators; package and publisher are well-established. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only prints a Windows usage tip; no network calls or arbitrary code execution. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.1.59 | 3 / 1 | |
| 0.1.53 | 3 / 1 | |
| 0.1.52 | 3 / 1 | |
| 0.1.51 | 3 / 1 | |
| 0.1.47 | 3 / 1 | |
| 0.1.44 | 3 / 1 | |
| 0.1.40 | 3 / 1 | |
| 0.1.33 | 2 / 1 | |
| 0.1.22 | 2 / 1 | |
| 0.1.20 | 2 / 1 | |
| 0.1.19 | 2 / 1 | |
| 0.1.18 | 2 / 1 | |
| 0.1.17 | 2 / 1 | |
| 0.1.16 | 2 / 1 | |
| 0.1.15 | 2 / 1 | |
| 0.1.14 | 2 / 1 | |
| 0.1.13 | 2 / 1 | |
| 0.1.12 | 2 / 1 | |
| 0.1.11 | 2 / 1 | |
| 0.1.10 | 2 / 1 | |
| 0.1.9 | 2 / 1 | |
| 0.1.8 | 2 / 1 | |
| 0.1.7 | 2 / 1 | |
| 0.1.6 | 2 / 1 | |
| 0.1.5 | 2 / 1 |
v0.1.53
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.52
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
2 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
3 findingsScript: node -e "if(process.platform==='win32')console.log('\nTip: run \"gcal assoc\" to associate .ics files with gcal')"
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobfrankston.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.