@apimatic/schema
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stale, long-lived publisher change consistent with legitimate org maintainer rotation. | ai | |
| source-diff | obfuscated-file:umd/schema.js | AI (source-diff): Terser-minified UMD build artifact per rollup-plugin-terser config, not injected obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Reflects standard build output (lib/es/umd dirs), not injected code. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap, no behavioral change; publisher has long clean track record. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.7.21 | 1 / 15 | |
| 0.7.20 | 1 / 15 | |
| 0.7.19 | 1 / 15 | |
| 0.7.18 | 1 / 15 | |
| 0.7.17 | 1 / 15 | |
| 0.7.16 | 1 / 15 | |
| 0.7.15 | 1 / 15 | |
| 0.7.14 | 1 / 15 | |
| 0.7.13 | 1 / 15 | |
| 0.7.12 | 1 / 15 | |
| 0.7.11 | 1 / 15 | |
| 0.7.10 | 1 / 15 | |
| 0.7.9 | 1 / 15 | |
| 0.7.8 | 1 / 15 | |
| 0.7.7 | 1 / 15 | |
| 0.7.6 | 1 / 15 | |
| 0.7.5 | 1 / 15 | |
| 0.7.4 | 1 / 15 | |
| 0.7.3 | 1 / 15 | |
| 0.7.2 | 1 / 15 | |
| 0.7.1 | 1 / 15 | |
| 0.7.0 | 1 / 16 | |
| 0.6.0 | 1 / 16 | |
| 0.5.1 | 1 / 7 | |
| 0.5.0 | 1 / 7 | |
| 0.4.1 | 1 / 7 |
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2024-04-04. It has since remained available on npm for 840 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2024-01-29. It has since remained available on npm for 906 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2023-12-18. It has since remained available on npm for 948 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2023-11-29. It has since remained available on npm for 967 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (wajahatiqbal) than the most recent previously approved version (mehdi991) on 2023-08-07. It has since remained available on npm for 1081 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2023-06-08. It has since remained available on npm for 1141 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2023-05-18. It has since remained available on npm for 1162 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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: maryamadnan3.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (mehdi991) on 2023-04-04. It has since remained available on npm for 1206 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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: mehdi991.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.