temporal-polyfill
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/common-a14efb97.mjs | AI (source-diff): Minified ESM build output; benign. | ai | |
| source-diff | obfuscated-file:dist/common-3078ba90.cjs | AI (source-diff): Minified build output of Temporal polyfill; no malicious behavior. | ai | |
| source-diff | obfuscated-file:chunks/internal.js | AI (source-diff): Minified bundle output; readable Temporal internal logic, no malicious behavior. | ai | |
| source-diff | obfuscated-file:chunks/classApi.js | AI (source-diff): Minified bundle output of Temporal class API; benign build artifact. | ai | |
| source-diff | obfuscated-file:dist/common-5e0be57a.mjs | AI (source-diff): Minified bundle output (short idents, no obfuscation signature); stable build artifact. | ai | |
| source-diff | obfuscated-file:dist/common-c41a489f.cjs | AI (source-diff): Minified CJS bundle, same benign build output. | ai | |
| source-diff | obfuscated-file:dist/common-c8d51eca.cjs | AI (source-diff): Minified CJS bundle output; standard for this build. | ai | |
| source-diff | obfuscated-file:dist/common-9bc60891.mjs | AI (source-diff): Minified bundle output with source maps; standard for this build. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env metadata change only; no behavioral risk for this trusted package. | ai | |
| source-diff | obfuscated-file:chunks/classApi-basic.js | AI (source-diff): Bundled ESM output with readable Temporal API names; not obfuscated. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump (0.x→1.x) restructured the package; expected growth. | ai | |
| source-diff | obfuscated-file:fns/ZonedDateTime.js | AI (source-diff): Bundled ESM output with readable Temporal API names; not obfuscated. | ai | |
| source-diff | obfuscated-file:chunks/funcApi-shim.js | AI (source-diff): Bundled ESM output with readable Temporal API names; not obfuscated. | ai | |
| source-diff | obfuscated-file:chunks/funcApi-native.js | AI (source-diff): Bundled ESM output with readable Temporal API names; not obfuscated. | ai | |
| source-diff | obfuscated-file:chunks/classApi-full.js | AI (source-diff): Bundled ESM output with readable Temporal API names; not obfuscated. | ai | |
| provenance | no-provenance | AI (provenance): Established package with a verifiable GitHub repo; lack of Sigstore provenance is common and not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:temporal-spec | AI (dependencies): temporal-spec is the companion type-spec package for the Temporal proposal, maintained by the same author/org. It is a benign dependency stable across versions of this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 2 / 0 | |
| 0.3.2 | 1 / 0 | |
| 0.3.1 | 1 / 0 | |
| 0.3.0 | 1 / 0 | |
| 0.2.5 | 1 / 0 | |
| 0.2.4 | 1 / 0 | |
| 0.2.3 | 1 / 0 | |
| 0.2.2 | 1 / 0 | |
| 0.2.1 | 1 / 0 | |
| 0.2.0 | 1 / 0 | |
| 0.1.1 | 1 / 7 | |
| 0.1.0 | 1 / 7 | |
| 0.0.8 | 1 / 7 | |
| 0.0.7 | 1 / 7 | |
| 0.0.6 | 0 / 7 | |
| 0.0.5 | 0 / 7 | |
| 0.0.4 | 0 / 7 | |
| 0.0.3 | 0 / 7 | |
| 0.0.2 | 0 / 7 | |
| 0.0.1 | 0 / 7 |
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arshaw.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
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: arshaw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
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: arshaw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arshaw.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arshaw.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arshaw.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arshaw.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
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: arshaw.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.